I setup the agentinstaller.msi to be deployed to workstations via GPO about a week ago. I tested it ahead of time and it worked great. I figured i'd apply it over the break as only a few people were going to be in sporatically and maybe i could flush out any issues before everyone got back this week. Last week went flawless and i had seen about as many computers as i expected registered with the vcenter console, and was awaiting today to see almost all of them.
Then I did something dumb and on monday rebooted the vcenter protect server to install some windows updates and didn't check to see if i came back up completely. Of course, it hadn't. The server was up but the vcenter protect service wasn't started. I didn't notice tihs today until mid-morning and by then most people were probably in. I started up the service, but i have only a few more computers than I did on monday (i expected ~150 more).
So I'm guessing what happened is the GPO installed the software, but coudln't register with the vcenter protect server so it isn't running on the machines but also won't be reinstalled again. A few questions I have is
1. am i lucky enough to think that maybe the service will try to re-register itself on next reboot of the machines?
2. Is there a way to tell the computers to re-register themselves through maybe a login script gpo, and if so is there any negative effect if it runs on a machine thats already been rergistered?
If anybody has any other ideas as to how to dig myself out of this predicament i'd love to hear them!