Network Administration

Network Administration tools:

 

~ Network Mapping tools ~

  • Cacti + PHP Weathermap

Create Maps of the Network with graphs that monitor ports

Create your own OID SMNP Data Collectors in Cacti using this reference http://docs.cacti.net/manual:087:3a_advanced_topics.3a_snmp_data_queries#snmp_data_queries

 

  • Switch Miner (http://switchminer.sourceforge.net)

Map each port on a Cisco switch with SNMP, you will need the switch IP address and Community String

  • The Dude (Reference for Usage and how to setup Probes https://aacable.wordpress.com/2011/12/13/monitoring-network-with-the-dude-pc-x86-or-mikrotik-npk-ver/)

Tools:

Network Packet & Switch Tracking (Link Runner alternative) https://netool.io

Network Security: Flingbox - https://www.youtube.com/watch?v=4Hc3YGsaW8U

 

 

~ Learning Managment Systems ~

  • Dokeos
  • Schoology (based on Drupal)
  • Janison CLP (NAPLAN Onlines framework)

A great LMS platform that is free to use.

  • Moodle
  • Open Edx
  • Canvus (free Edition)

 

~ News Websites ~

    VMware Information

     https://www.vladan.fr

     http://www.vmwarearena.com 

     http://www.virtualizationteam.com

    http://blog.cactiusers.org

    http://gregsowell.com

    http://www.vmwarebits.com

 

     Microsoft News

     http://techgenix.com

 

     SysAdmin

     http://blackbird.si

https://github.com/kahun/awesome-sysadmin

 

     Technical Hub

      https://evotec.xyz/hub/ 

      https://www.techadvisor.co.uk/

 

Network Diagrams

http://go.drawthe.net

https://www.edrawsoft.com/networkdiagram/

 

Asset Management

http://ralph.allegro.tech

https://github.com/digitalocean/netbox

 

~ Training ~

Mikrotik

http://gregsowell.com/?page_id=951

Cacti

http://gregsowell.com/?page_id=86

 

 

 

~ Scripting & Auditing ~ 

https://www.shellandco.net

Auditing Group and User changes in Active Directory: https://evotec.xyz/hub/scripts/get-eventslibrary-ps1/ https://evotec.xyz/hub/scripts/get-eventslibrary-ps1/

Auditing Group Membership: https://github.com/lazywinadmin/Monitor-ADGroupMembership

 

Powershell:

https://github.com/dwj7738/My-Powershell-Repository/tree/master/Scripts

https://floobits.com/PoshCode/PowerShell.Slack.com/

Find Users Actively Connected to a Share (Computer Management -> 

https://thescriptlad.com/2011/08/29/find-users-actively-connected-to-a-share/

Get a list of Failed Login Attempts

https://gallery.technet.microsoft.com/scriptcenter/Failed-Logins-Report-ccf071a9

https://community.spiceworks.com/topic/1927863-powershell-get-open-sessions-attributes-info

Find OpenFiles and save them to CSV

openfiles /query /fo CSV /v > C:\Scripts\openfiles.csv

to include date

$CurrentDate = Get-Date
$CurrentDate = $((Get-Date).ToString('MM-dd-yyyy_hh-mm-ss'))
openfiles /query /fo CSV /v > C:\Scripts\openfiles_$CurrentDate.csv

exe alternative: https://www.nirsoft.net/utils/network_opened_files.html

 

https://stackoverflow.com/questions/1795679/determine-users-accessing-a-shared-folder-using-powershell

$computer = "LocalHost"

$namespace = "root\CIMV2"

$userSessions = Get-WmiObject -class Win32_ServerConnection -computername $computer -namespace $namespace

 

if($userSessions -ne $null)

{

    Write-Host "The following users are connected to your PC: "

 

    foreach ($userSession in $userSessions)

    {

        $userDetails = [string]::Format("User {0} from machine {1} on share: {2}", $userSession.UserName, $userSession.ComputerName, $userSession.ShareName)

        Write-Host $userDetails

    }    

 

    Read-Host

}

The following articles were useful:

 

Automatic Rename and Rejoin to Domain with Powershell (no restart required)

http://kunaludapi.blogspot.com/2016/03/powershell-rocks-rejoin-computers-in.html#at_pco=smlwn-1.0&at_si=5bd0fea552c9d5c5&at_ab=per-2&at_pos=0&at_tot=1

 

Find out when a computer was added to the Domain:

All computer accounts that were created as of December 1, 2011 (12/01/2011) in the Active Directory:

Get-ADComputer -LDAPFilter "(&(objectCategory=computer)(whenCreated>=20111201000000.0Z))" -Properties whenCreated | Format-Table Name,whenCreated,distinguishedName -Autosize -Wrap

source: https://serverfault.com/questions/646111/find-computers-recently-joined-to-active-directory

 

What is %~dpn0?

 

PowerShell.exe -Command “& ‘%~dpn0.ps1′” actually runs the PowerShell script. PowerShell.exe can of course be called from any CMD window or batch file to launch PowerShell to a bare console like usual. You can also use it to run commands straight from a batch file, by including the -Command parameter and appropriate arguments. The way this is used to target our .PS1 file is with the special %~dpn0 variable. Run from a batch file, %~dpn0 evaluates to the drive letter, folder path, and file name (without extension) of the batch file. Since the batch file and PowerShell script will be in the same folder and have the same name, %~dpn0.ps1 will translate to the full file path of the PowerShell script.

For example, running a powershell script within a bat file like so, will create a log file with the same name as the bat file: PowerShell.exe -ExecutionPolicy Bypass -Command "& {%~dpn0.ps1 -Verbose}" > %~dpn0.log

https://www.howtogeek.com/204088/how-to-use-a-batch-file-to-make-powershell-scripts-easier-to-run/

 

Create and pass a secure Password with Powershell:

"Password!" | ConvertTo-SecureString -AsPlainText -Force | ConvertFrom-SecureString | Out-File "C:\Securefolder\Password.txt"

$pass = Get-Content "C:\Temp 2\Password.txt" | ConvertTo-SecureString

 

Example:

$password = Get-Content "C:\User\Desktop\Password.txt" | ConvertTo-SecureString
$LiveCred = New-Object System.Management.Automation.PsCredential('username',$password)

Source: https://www.pdq.com/blog/secure-password-with-powershell-encrypting-credentials-part-1/

 

~ Preinstalled Virtual Machines ~

  • Bitnami Stacks

 

 ~ Purchasing ~

Cheap Dubix 
https://rapidoptics.com.au/lr-10gbase-lr/69-cisco-compatible-10gbase-lr-1310nm-sfp-transceiver.html

From RapidOptics Support: The difference between our products and genuine Cisco SFPs? In terms of functional differences, they're manufactured to meet the same standards as Cisco SFPs - those are I believe actually produced by a company called Finisar - so there's no practical difference and that's how we can guarantee compatibility. The difference between our Cisco compatible and our generic compatible modules is that we add the vendor-specific codes that Cisco devices look for (otherwise they wouldn't accept the SFP, like if you put a Juniper SFP into a Cisco device the cisco device wouldn't accept it because it would look for a Cisco coding)

http://www.fs.com/products/11555.html

 

 ~ Programming ~

Python

Problem-Solving with Algorithms and Data Structures

http://interactivepython.org/courselib/static/pythonds/index.html

Javascript

https://github.com/AllThingsSmitty/must-watch-javascript

Paste Bins

All Round

https://bpaste.net

Programming Paste

http://dpaste.com

Javascript

http://jsbin.com/?html,output

File transfer

transfer.sh 

 

Fixed: where are my Office 365 AutoRecovery files?

Question :

I accidentally messed up the Office documents (Word/PowerPoint/Excel) I was working on, and I didn’t save it before, so I wanted to get the auto-saved version from the AutoRecovery-folder as I’ve done in the old days of Office 2008 and 2004.

But now I am using Office 365, and I can’t find the AutoRecovery folder anywhere… where is it ?

Answer :

You might have guessed: nowadays, the AutoRecovery-folder is located in an entirely different location on your Mac.

If you are running Office 2011 for Mac (whether as part of Office 365 or not) the correct path to the AutoRecovery-folder is this :

~/Users/username/Library/Application Support/Microsoft/Office/Office 2011 AutoRecovery

And if you are running Office 2016 for Mac (whether or not as part of Office 365) the correct path to the Word 15‘s AutoRecovery-folder(s) is :

~/Users/username/Library/Containers/com.microsoft.Word/Data/Library/Preferences/AutoRecovery/

for PowerPoint 15 the correct path is :

~/Users/username/Library/Containers/com.microsoft.PowerPoint/Data/Library/Preferences/AutoRecovery/

and for Excel 15 the correct path is :

~/Users/username/Library/Containers/com.microsoft.Excel/Data/Library/Preferences/AutoRecovery/

BEWARE : it’s not straight-forward to get to this folder in recent/current versions of OSX and macOS, as the user’s Library-folder is a hidden folder. So if you want to access it, the easiest way to do so is :

– in the Finder, click on “Go” in the top menu bar

– when the pulldown menu appears, press the ALT-key on your keyboard (a.k.a. OPTION-key) and an extra option named “Library” will appear in the pulldown menu

– while holding the ALT-key, click on “Library” and your personal (hidden) Library-folder will open in the Finder

– there you can navigate further using the paths listed above to find the AutoRecovery-folder you’re looking for

That’s it.

Enjoy !

 

Viewing Sessions in Server 2012 R2

http://wm-help.net/lib/b/book/1299397998/91

http://www.stevemiller.net/sharewatch/

https://www.nirsoft.net/utils/network_opened_files.html

 

Information

Why do Routers and Modems require so much horsepower, it is to do with TCP Offloading, read more about it here: https://en.wikipedia.org/wiki/TCP_offload_engine

 

SCCM Secondary Server Guides:

 
https://www.systemcenterdudes.com/sccm-2012-secondary-site-installation/
 
http://richardbalsley.com/how-to-install-secondary-sites-in-system-center-configuration-manager-2012
 
Troubleshooting SCCM installs:
 
https://blogs.technet.microsoft.com/sudheesn/2010/05/31/troubleshooting-sccm-part-i-client-push-installation/
 
 
 
Device Collection Queries 

The following WQL query will add the machines to a collection based on their naming conventions. This query is useful if we want to add only some machines to a collection using WQL query based on the computer starting names (ABC-XXXX) or machines named using business unit (HR-XXXXXX).

Change the values ( ABC and DEF ) as your requirements.

*********************************************************************************

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.Name like "%HR%" or SMS_R_System.Name like "%ABC%" or SMS_R_System.Name like "%DEF%"

*********************************************************************************

 
http://eskonr.com/2012/06/sccm-collection-to-use-wildcard-in-string-matching/
 
 
Change Site Code:
http://eddiejackson.net/wp/?p=13582
 
 

SCCM Collection queries

source: http://venusingireddy.blogspot.com/2012/12/sccm-collection-queries.html && http://eskonr.com/2012/06/sccm-collection-to-use-wildcard-in-string-matching/

This post provides various WQL queries to generate custom SCCM collections (07/12) to group the machines in a collection.

All of the queries from this post have tested in my lab. If you see any errors in a query please post a comment so I can fix them.

This page will be updated periodically.

Please note; when you are copying a query from a web browser you need to make sure that the browser is not adding any extra characters.
SCCM Collection query for various models in one  collection:
The following WQL query will populate a collection with  all the dell Latitude and XPS models. Change the models names as required.
******************************************************************************
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,
SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,
SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.Model like "Latitude%" or SMS_G_System_COMPUTER_SYSTEM.Model like "XPS%"
*******************************************************************************
SCCM Collection query for all workstations: 
The following WQL query for SCCM will poplulate all the workstaions into one collection.
This query will be useful when 
*******************************************************************************
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like "Microsoft Windows NT Workstation%"
 *******************************************************************************

SCCM Collection query to get 32 bit and 64 bit machines:

This WQL query will create a SCCM collection for all the 64 bit Workstations in the organization.

To create a collection for 32-bit workstations, replace the “x64” with “X32”.

*********************************************************************************

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_SYSTEM.SystemType = "X64-based PC"

*********************************************************************************

SCCM Collection query for a PC model:

This WQL query will create a SCCM collection for all the VMWare Workstations in the organization.

To create a collection for specific model workstation, replace the “VMware virtual Platform” with a model name of the machine you want to create a collection.

*********************************************************************************

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.Model like "VMware Virtual Platform"

*********************************************************************************

SCCM Collection query for Windows 7 machines in multiple domains:

This query makes a collection of all Windows 7 machines on different domains.

You can rename DOMAIN1 to DOMAIN5 as you needed.

************************************************************

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where

 

(SMS_R_System.ResourceDomainORWorkgroup like "DOMAIN1" or SMS_R_System.ResourceDomainORWorkgroup like "DOMAIN2" or SMS_R_System.ResourceDomainORWorkgroup like "DOMAIN3" or SMS_R_System.ResourceDomainORWorkgroup like "DOMAIN4" or SMS_R_System.ResourceDomainORWorkgroup like "DOMAIN5") and SMS_R_System.OperatingSystemNameandVersion like "Microsoft Windows NT Workstation 6.1"

************************************************************

SCCM Collection for Windows 7 machines from a OU and multiple domains:
This WQL Query will create a collection for all Windows 7 machines with combination of OU and domains.

*********************************************************
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where 
(SMS_R_System.SystemOUName like "AD.YOURDOMAIN.COM/OU" or SMS_R_System.ResourceDomainORWorkgroup like "DOMAIN1" or SMS_R_System.ResourceDomainORWorkgroup like "DOMAIN2")and SMS_R_System.OperatingSystemNameandVersion like "Microsoft Windows NT Workstation 6.1"

*********************************************************

SCCM Collection for Laptops: 

Below WQL query creates a collection for all the laptops in the environment based on the System Enclosure attribute and Chassis type.

*********************************************************

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_SYSTEM_ENCLOSURE on SMS_G_System_SYSTEM_ENCLOSURE.ResourceId = SMS_R_System.ResourceId where SMS_G_System_SYSTEM_ENCLOSURE.ChassisTypes like "8 , 9, 10, 11, 12, 14, 18, 21"

**********************************************************

SCCM Collection for Desktops:

Below WQL query creates a collection for all the desktops in the environment based on the System Enclosure attribute and Chassis type.

***********************************************************

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_SYSTEM_ENCLOSURE on SMS_G_System_SYSTEM_ENCLOSURE.ResourceID = SMS_R_System.ResourceId where SMS_G_System_SYSTEM_ENCLOSURE.ChassisTypes like "('3','4','5','6','7','15','16')"

************************************************************

SCCM Collection query for inactive workstations:

Below WQL query creates a collection with all inactive machines for 90 days in the environment. The 90 days can be modified as required by editing the last line of the query.

*************************************************************

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.Name in (select Name from SMS_R_System where ((DATEDIFF(day, SMS_R_SYSTEM.AgentTime, getdate()) >=90) and AgentName = "SMS_AD_SYSTEM_DISCOVERY_AGENT")) and SMS_R_System.Name in (select Name from SMS_R_System where ((DATEDIFF(day, SMS_R_SYSTEM.AgentTime, getdate()) >=90) and AgentName = "Heartbeat Discovery"))

************************************************************* 

SCCM Collection query for machines not rebooted in last30 days:

This is an easy WQL query to get the machine details which hasn’t been re-booted for 30 days.

 

We can change the 30 days at end of the statement to adjust desired days.

This query is targeted only for workstations such as XP, Vista and Windows 7.

 

*********************************************************

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId where (SMS_G_System_OPERATING_SYSTEM.Caption like "%xp%" or SMS_G_System_OPERATING_SYSTEM.Caption like "%vista%" or SMS_G_System_OPERATING_SYSTEM.Caption like "%windows 7%") and (DateDiff(day, SMS_G_System_OPERATING_SYSTEM.LastBootUpTime, GetDate()) >30)

********************************************************** 

SCCM Collection query for no client machines:

The following SCCM Collection query is useful when you have many machines without SCCM Client on the client machines.

Just create a new collection using the below query;

***********************************************************

select R.ResourceID,R.ResourceType,R.Name,R.SMSUniqueIdentifier,R.ResourceDomainORWorkgroup,R.Client from SMS_R_System as r full join SMS_R_System as s1 on s1.ResourceId =   r.ResourceId full join SMS_R_System as s2 on s2.Name = s1.Name where s1.Name   = s2.Name and s1.ResourceId != s2.ResourceId and R.Client = null

***********************************************************

SCCM Collection Query to get Duplicate Hostnames in SCCM console:

The following WQL query will add all the machines with duplicate machine name.

***********************************************************

select R.ResourceID,R.ResourceType,R.Name,R.SMSUniqueIdentifier,R.ResourceDomainORWorkgroup,R.Client from SMS_R_System as r full join SMS_R_System as s1 on s1.ResourceId =   r.ResourceId full join SMS_R_System as s2 on s2.Name = s1.Name where s1.Name   = s2.Name and s1.ResourceId != s2.ResourceId and R.Client = null

****************************************************************
SCCM Collection query computer name:

The following WQL query will add the machines to a collection based on their naming conventions. This query is useful if we want to only some machines to a collection using a query with starting names (ABC-XXXX) or machines named using business unit (HR-XXXXXX).

Change the values ( ABC and DEF ) as your requirements.

*************************************************************************

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.Name like "%HR%" or SMS_R_System.Name like "%ABC%" or SMS_R_System.Name like "%DEF%"

********************************************************************

 

 

Cisco Switch Changing the MTU:

 

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst2960x/software/15-0_2_EX/int_hw_components/configuration_guide/b_int_152ex_2960-x_cg/b_int_152ex_2960-x_cg_chapter_0110.pdf

 

VCSA 6.5 reset root password

It’s always a very annoying situation when you can’t login into a system anymore because you either don’t know the root password anymore or the system is not able to log you in. The latter can happen if the root mountpoint of the VCSA 6.5 appliance filled up.

As VCSA (vCenter Server Appliance) 6.5 is build on top of Photon OS, you can’t use the same standard procedure you know from Debian, Ubuntu or RedHat. But relax, it’s very simple to reset the root password or clean up a filled up root partition.

 

First thing to do is to restart your vCenter appliance and wait for the Photon OS Splash screen during boot. 

 

VCSA Splash Screen reset root password

 

Hit the letter e to enter the boot menu.

Then change to the GNU GRUB boot menu editor and hit enter.

 

VCSA Grub menu

 

Next is to add the following string behind the line that starts with linux: rw init=/bin/bash

 

boot line to vcsa root reset password

 

Hit the F10 function key to boot the changed entry.

Clean up the root partition

In many cases you should check the root partition usage, using the df -h command. Very often the log files grew large and filled up your partition. One well known guy is the audit.log in /var/log/audit. So type ls -sh /var/log/audit to check the file size and rm /var/log/audit/*.log to clean it up.

Reset the root password

If you’re sure that you have to reset the root password, please follow these steps:

passwd 

then enter a strong password twice and remember it.

umount /

reboot -f

It is important to add the -f behind the reboot.

source: https://www.opvizor.com/vcsa-6-5-reset-root-password

 

 

 

Step-by-Step: Upgrading to VCSA 6.7

[Click on image for larger view.] Figure 12. Importing historical data.

The last step in the wizard was to verify the information I had entered and that the existing VCSA had been backed up (Figure 13).

[Click on image for larger view.] Figure 13. Ready to complete Stage 2.

After about 30 minutes, a screen appeared saying that Stage 2 had completed; the page also included an Appliance Getting Started Page link (Figure 14).

[Click on image for larger view.] Figure 14. Upgrade completed.

Post-Upgrade VCSA 6.7
Once the upgrade had completed, I clicked the Appliance Getting Started Page link. This page gave me the option to go to the vSphere Client, vSphere Web Client, and vSphere documentation, to see the functionality updates for the vSphere Client, as well as to browse my datastore and learn about the vSphere Web service SDK (Figure 15).

[Click on image for larger view.] Figure 15. VCSA launch page.

The Functionality Updates for the vSphere Client page (Figure 16) is quite helpful as it shows what workflow functionality is not yet available in the vSphere Client. I browsed this page and then found myself returned to it occasionally to see if what I was trying to accomplish was doable in the vSphere Client. If you want to visit this page without going through the client, you can find it here (I suggest that you bookmark this link).

[Click on image for larger view.] Figure 16. vSphere Client functionality.

The next thing I did was go to the vSphere Client. As a visual indicator, the vSphere Client has a black border (Figure 17) while the vSphere Web Client is framed in blue (Figure 18).

[Click on image for larger view.] Figure 17. vSphere Client framed in black.
[Click on image for larger view.] Figure 18. vSphere Web Client framed in blue.

Backup Scheduler
vSphere has provided a tool to back up the VCSA since vSphere 6.5; however, this tool was limited. Furthermore, the 6.7 release includes a new scheduling tool (Figure 19), which allows you to back up the data on a specific schedule and set a retention policy. For more information on setting up and using the VCSA backup tool, be sure to see my previous article here.

The VCSA backup scheduler can be accessed from the VMware Appliance Management Interface (VAMI) UI. To access the VAMI, append :5480 to the end of the URL IP address of the VCSA (for example, VCSA67.Fentronics.local:5480).

[Click on image for larger view.] Figure 19. vSphere 6.7 VCSA backup scheduler.

Monitoring VCSA
The VAMI also has a new monitoring tool for vSphere, which can be accessed by clicking the Monitor tab located on the left of the VAMI page (Figure 20). From this page, you can toggle through CPU & Memory, Disk, Networking, and Database tabs to monitor VCSA activity.

 

[Click on image for larger view.] Figure 20. VCSA monitoring.

From the VCSA Monitor tab, you can see activity for the last hour, day, week, month, quarter or year.

Patching VCSA
All software will eventually need to be patched, and the VCSA is no exception. Fortunately, VMware has made it very simple to patch the VCSA, and I'll walk you through the steps that I took to do so.

A few weeks after installing my VCSA, I noticed that an update was available for it. To update my VCSA, I went to my VAMI and logged into it as root. I then clicked Update, and after a short wait it showed that there was a critical update available (Figure 21).

I clicked Stage Only (I tried Stage and Install but it failed), which downloaded the update from VMware.

[Click on image for larger view.] Figure 21. The Update menu.

 

After the update was downloaded and the staging was complete, I clicked Install (Figure 22).

[Click on image for larger view.] Figure 22. Installing the update.

I then needed to accept the EUL, opt to join or not join VMware's Customer Experience Improvement Program (CEIP), and acknowledge that I had backed up my VCSA. The installation process then stopped the services currently running on the VCSA, installed the patches, and then restarted the services. After the installation completed, I received a message that the installation succeeded (Figure 23). While the update was in progress, the vSphere Client displayed a message that the vSphere Client was being updated and then initializing. When I logged back in to the vSphere Client, I saw that it had been updated successfully.

[Click on image for larger view.] Figure 23. Installation completed successfully.

Final Thoughts
It took me approximately half an hour to upgrade my VCSA from version 6.5 to 6.7 without any issues; overall, a smooth and seamless process. If you have a larger infrastructure I'm sure that it will take more time, and if you have a complex environment it will take more planning to execute a seamless upgrade. I haven't seen many issues reported by the community regarding vSphere 6.7 VCSA, a good indication that the updated version is stable.

Due to enhancements to VCSA version 6.7, in particular its performance and vSphere Client, you may want to consider upgrading your VCSA sooner rather than later.

source: https://virtualizationreview.com/Articles/2018/07/19/Upgrading-to-VCSA-6.7.aspx?Page=2

-->
© Donald Young HTML Responcive Template designed by Crazy Pixels