It should never happen that way but this is why I wanted the window to not display any text off) and start the powershell in a minimized state (/min) as well if you notice in the PowerShell the Out-Null so it doesn’t show the user the output of the vCenter once it connects.
I wanted this to not cause any problems if it some reason ran slower and the off chance it kicked off when a user logged in. Start /min powershell c:\scripts\vm-tag.ps1
Next we will need to create the bat file that will kick off the above script, I called my “post-sync.bat” so that I’ll easily know what that is going forward. New-TagAssignment -Tag $NPTag -Entity $ComputerName $ComputerName = "$env:computername" # GET COMPUTER NAMEĬonnect-viserver -Server $vc -user $userTag -password $passTag | Out-Null Also didn’t think the Windows Credential Store would either in this scenario but may test it later. I wasn’t sure the Get-Credentials that I normally use would work since the parent will fork/clone and the encrypted file won’t work on the child VMs. If your scenario is different then we will need to find another way to match these so we can automate this process. This is critical that the Computer Name of the OS matches what the VM name will be so we can add the tag to vCenter. Here you will define the variables for your vCenter, the tag that we created above, the username and password for the local user we created with the Tagging Admin privileges and then the Computer Name. bat/.vbs/.cmd files.īelow is my VM-Tag.ps1 script. The Horizon post-sync process can only use.
On the parent create a folder where we will keep the PowerShell script and bat file that we will use to kick off the file.
0 kommentar(er)
