Kaviza VDI in a Box extra Computers in AD

Problem: At some point Kaviza or VDI in a Box did not remove deactivated computers from AD either due to an improper shutdown, timing issue,… finding out which are in use and are not can take some time. Here is how I sped up the cleanup process.

Solution: Follow the steps below to export your computer names to bat log file. Then edit the bat file to ping the systems and export to a log file then review the results and clean up ad.

All of my Kaviza systems have the same prefix of FBWKVFB-x so I ran the following command to pull the list from AD and export to a bat file:

Dsquery computer domainroot –name FBWKVFB-* > c:\kavizapc.bat

then edit the bat file and use the find and replace command to replace the excess fields. Here is an example of the unedited output:

"CN=FBWKVFB-7C246DT,OU=SBComputers,OU=Computers,OU=MyBusiness,DC=ad,DC=domain"

Find
“CN=
Replace with
Ping –4    
                              
Note: the “-4” command is to use IPV4 ping only if you want to ping IPV6 only use –6 instead

Find
OU=SBComputers,OU=Computers,OU=MyBusiness,DC=ad,DC=domain”s”
Replace with
>> C:\kavizaping.txt

On the first line remove the first “>” so it will look similar to this:

Ping FBWKVFB-7C246DT> c:\Kavizaping.txt
Ping FBWKVFB-114URFF>> c:\Kavizaping.txt

You can now run the Kavizapc.bat and view the output in C:\Kavizaping.txt:

Ping request could not find host FBWKVFB-7C246DT. Please check the name and try again.
Ping request could not find host FBWKVFB-114URFF. Please check the name and try again.

Any of the desktops that failed to ping are likely your excess systems that need removed.

Note: Just because they pinged does not mean they are still valid as your DNS records may not be up to date. If in doubt use the ping logs to do a reverse query for example here is a positive result:

Pinging FBWKVFB-MJJLD4K [192.168.100.100] with 32 bytes of data:
Reply from 192.168.100.100: bytes=32 time=3ms TTL=128

To confirm that IP really is FBWKVFB-MJJLD4K you can run the following command:

Ping –a 192.168.100.100

The first line of the results should show you the same PC name:

pinging FBWKVFB-MJJLD4K.ad.domain [192.168.100.100] ….

Comments

Post a Comment

Popular posts from this blog

Office 365 Deployment Tool Office Download fails “Could not Install”

Image
Problem: you run the setup.exe /download download.xml and fails immediately with “Couldn’t install” You make sure all the settings are correct (see other blogs) and find nothing wrong Solution: Change drives and run it as an administrator again. For example above i am in the F:\OfficeDeploy directory which is the same directory I have the download.xml directing the download to. If i Change to the c: and run the same command again it works The Office Data folder was created and updated as shown below:
Read more

FRS to DFSR Post Cleanup “File Replication NtFrs Stopped”

Image
After successfully migrating from FRS to DFSR you get the File Replication NtFrs service is Stopped error on the local servers AD DS Services list. In the Event logs you may see Event id 13575 13577. You can confirm your migration completed by opening a cmd prompt as administrator and typing in: dfsrmig /getmigrationstate After your migration to DFSR is completed and you have given your servers ample time to propagate this service is no longer required. Since it is set to “Automatic”, as shown below” it shows in logs as a false positive error. Edit the File Replication Service and change it to “Disabled”, as shown below: Once it is listed as “Disabled” it will no longer show in the Console as an “error” Note : it may take some time to clear from the active view
Read more

Domain Migration SubinACL /Migratetodomain How To:

Caution : DO NOT run this on Domain Controller C:\ and only run on roaming profiles folders, or my docs shares day of migration to avoid ownership change issues. Confirm Domain trust is in place and users and groups have been migrated Test ping of olddomain.org from new domain Test ping of newdomain.org from olddomain Add newdomain.org domain controller host records to olddomain.org including reverse DNS records Confirm the user running the app is a domain admin in BOTH domains Download SubinACL here: http://www.microsoft.com/en-us/download/details.aspx?id=23510 /Migratetodomain- command will add the permissions of the new user to the old files and folders for example if jimbob@olddomain.org was migrated to the new domain jimbob@newdomain.org and you run the command below any file or folder in that path that has jimbob@olddomain.org will add Jimbob@newdomain.org with the exact same permissions. This is a safer way to migrate by keeping the old and new permissions intact while a
Read more