Hi Jason, it’s good to hear from you. To answer your question “is it reprovisioned with all the same identity info (MAC addresses, serial number, UUID)”, I would have to dig more into it if I still see these PVS virtual servers are still coming in since I have implemented a solution to remove the BigFix Client last week.
I will give you more information if I found some duplicate servers.
Technically and logically speaking and thinking, why would the BigFix Client needs to re-create a new ID if someone restore the snapshot? That part is really not making sense. If a virtual server with BigFix Client installed and snapshot was taken as usual in virtual environment, it should and must remain the same BigFix Client ID after a snapshot restored. Think of it, it is coming from the same server image. It can’t be recreating a new client ID after each snapshot restored. In fact, I can understand if BigFix Client was reinstalled and a new client ID is created. That makes a lot more sense.
On top of that, I would expect to see the same information such as VMWare UUID, MAC address, IP and hostname after the snapshot restored. So why does it need to create a new client ID?
It is just those steps described to deal with duplicate computers are completely NOT making sense to do extra work manually (preserving and restoring…).
HCL is a big company as IBM. Personally speaking when this issue is reported by a customer, I would expect it to conduct a full test to see how the Citrix PVS works and behaves.
HCL needs to come up a better logical way to deal with duplicate computer issue as it is also affecting other virtualization vendors such as VMWare and Hyper-V.