rbennett806
Posts: 732
Score: 11 Joined: 6/14/2006 Status: offline
|
This may sound bad right off the bat, but what I do is run my basic OS tests right within our production environment. Since I can control who gets what I don't have to worry about a production machine getting my test OS advertisement, and since I'm not doing anything extreme I don't have to worry about blowing up the SMS/SCCM server (if I'm getting THAT extreme at this stage I need to ask myself what I'm doing; because things are running smoothly now). So what I've got are 4 sets of OS-based setups within my production environment: 1 Windows XP TEST 1 Windows Vista TEST 1 Windows XP PRODUCTION 1 Windows Vista PRODUCTION Once I run my tests and have a new .WIM file I want to kick out to production I simply rename/move it to replace my existing production .WIM file after backing the production file up somewhere else (making any other related changes that might be necessary depending on what I'm doing - like tweaking my unattend.xml file or something like that), and then update my production DPs and I'm all done. At least, roughly that's the process...
|