SMS management of Virtual PC Clients
Gidday Forum,
Some advice required.
Has anyone had any experience with SMS management of virtual PC's on a network?
We are unsure if SMS (2003 SP1) will reinventory a virtual PC if Undo disks are enabled. Are there any considerations we need to ensure to properly manage virtual PC's. If the developer runs through multiple system starts during the day, how will SMS handle the collections / inventories etc.
Any advise or otherwise, greatly appreciated.
cheers
Wayne
Some advice required.
Has anyone had any experience with SMS management of virtual PC's on a network?
We are unsure if SMS (2003 SP1) will reinventory a virtual PC if Undo disks are enabled. Are there any considerations we need to ensure to properly manage virtual PC's. If the developer runs through multiple system starts during the day, how will SMS handle the collections / inventories etc.
Any advise or otherwise, greatly appreciated.
cheers
Wayne
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
revizor
18 years ago
Posted by:
WayneB
18 years ago
Thanks Revizor,
From your post I gather that once the SMS advanced client has done it's first inventory then that should be saved to the virtual hard disk. Subsequently any scheduled inventories would not be neccessary (could be governed by separate SMS policy?) as the virtual PC inventory would not change.
An aside question for anyone reading this, how do you mange your licensing requirements for Windows and Office etc. on the virtual PC, in a network scenario? I'm envisaging we could have up to 50 developers using a multitude of O/S's ranging from W2K to XP SP2, any suggestions on how that can be best managed using SMS?
Thanks
Wayne
From your post I gather that once the SMS advanced client has done it's first inventory then that should be saved to the virtual hard disk. Subsequently any scheduled inventories would not be neccessary (could be governed by separate SMS policy?) as the virtual PC inventory would not change.
An aside question for anyone reading this, how do you mange your licensing requirements for Windows and Office etc. on the virtual PC, in a network scenario? I'm envisaging we could have up to 50 developers using a multitude of O/S's ranging from W2K to XP SP2, any suggestions on how that can be best managed using SMS?
Thanks
Wayne
Posted by:
revizor
18 years ago
WayneB, did you mean software/hardware inventory, or computer accounts inventory inside the SMS infrastructure?
I assumed you were asking about the sw/hw inventory...
For the computer accounts inventory, it should still hold true, with minor deviations.
Out of curiosity, are your virtual PCs on AD? What are the discovery methods in SMS? Client push methods?
Also, what is the use of SMS client on those virtual PCs? - I'm asking because in our environment, we keep SMS client off the virtual PCs to have those "non contaminated"...
I assumed you were asking about the sw/hw inventory...
For the computer accounts inventory, it should still hold true, with minor deviations.
Out of curiosity, are your virtual PCs on AD? What are the discovery methods in SMS? Client push methods?
Also, what is the use of SMS client on those virtual PCs? - I'm asking because in our environment, we keep SMS client off the virtual PCs to have those "non contaminated"...
Posted by:
WayneB
18 years ago
Gidday Revizor,
Thanks for replying. Yep, our virtual PC's are on the AD, so that we can test apps packaged with applied group policy. Our discovery methods are policy based hw and sw inventory once a day. Nothing is client pushed unless absolutely neccessary and extensive testing regime undertaken with critical apps on the network.
We would like to manage the increasing numbers of VPC coming onto the network with some guidelines and shift them into their own developmnet container when placed on the network. Also to manage the software licensing issues which is real "challenge" at the moment. the licensing for each O/S means some business units have to cough up the extra dosh for O/S and Office.
Cheers
Wayne
Thanks for replying. Yep, our virtual PC's are on the AD, so that we can test apps packaged with applied group policy. Our discovery methods are policy based hw and sw inventory once a day. Nothing is client pushed unless absolutely neccessary and extensive testing regime undertaken with critical apps on the network.
We would like to manage the increasing numbers of VPC coming onto the network with some guidelines and shift them into their own developmnet container when placed on the network. Also to manage the software licensing issues which is real "challenge" at the moment. the licensing for each O/S means some business units have to cough up the extra dosh for O/S and Office.
Cheers
Wayne
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.