Managing VMWare View clients with ConfigMgr ??
- Hi,
has anyone made any experiences with this constellation?
My customer has around 1200 virtual clients (XP SP3) in a VMWare View environment.
For patching purposes the machines are taken offline and then inserted again. Same thing with crashed machines. They reset those machines and I wonder if there will be problems with the ConfigMgr GUID.
Any hint would be nice
Miguel Rodriguez MCTS - ConfigMgr ~~elmunjo.blogspot.com~~
Todas las respuestas
- Need to be tested, but I think you should be fine if you let conflicting records merge the records:"ELMUNJO" <=?utf-8?B?RUxNVU5KTw==?=> wrote in message news:db8a300f-da9b-497 b-b667-6e3becfc9910...Hi,
has anyone made any experiences with this constellation?
My customer has around 1200 virtual clients (XP SP3) in a VMWare View environment.
For patching purposes the machines are taken offline and then inserted again. Same thing with crashed machines. They reset those machines and I wonder if there will be problems with the ConfigMgr GUID.
Any hint would be nice
Miguel Rodriguez MCTS - ConfigMgr ~~elmunjo.blogspot.com~~
With a little further investigating i found out the following:
VMWare View clients are deleted from AD and recreated for the following purposes:
-Patching the master Image
-Reinstalling in case of corrupted client
So the ConfigMgr tasks will have to be configured exactly:
Delete Inactive Client Discovery Data
(and Delete Aged Discovery Data)
I will post an update as soon as i have exact results.
Thanks for your thoughts.
Miguel Rodriguez MCTS - ConfigMgr ~~elmunjo.blogspot.com~~Update:
Using the built-in Tasks won't work for this constallation.
What VMWare View does:
Old client is deleted from AD
Client is recreated with the same DNS Name but new HW config
Client comes up with Configmgr Client and new SMS UUID + new HW ID + new MAC
we have 2 records in DB, both active
As my customer has both virtual and physical clients i don't know if i can lower the delete inactive client disc data task as that would also remove clients from users that are on vacation for a longer period.
Normally those double entries would be removed after 60 days via the task.
we have Heartbeat set to 1 day
Is there any other way of getting rid of the old entries?
When I activate AD System Disc running each day, would that enable me to lower the del inact. client disc data task interval?
Let's say:
Heartbeat: 1 day
AD System: 1 day
del inact. client disc data: 1 Week
The old machines would be removed after 1 week because neither disc. method would find him
All other machines would be heartbeated or (if offline for a longer period) found via AD System Disc.
Would that work, or am I missing something?
Will those intervals do any harm to my environment?
Miguel Rodriguez MCTS - ConfigMgr ~~elmunjo.blogspot.com~~
