millerr

I solved it... Yes on a Sunday... at the office. At least I can sleep well tonight knowing that it will work when I formally deploy. Run WINSAT PREPOP at an elevated command prompt. AERO was enabled by default now.

I did read this, but would prefer to figure out why it is happening in the first place.

It is crazy, because it worked just fine on another deployment... haha

Happy Saturday everyone. I'm having an issue when deploying Windows 7 in conjunction with mdt. The aero theme is not applied to new users despite running the wei and using copyprofile in the unattend xml. But if the user right clicks on the desktop and chooses aero it works? What is confusing is that it worked perfectly on the fleet of laptops I just deployed. I have also set persistdrivers to true in the xml. Any ideas? Thanks

The sysvol location is there for policydefinitions, so I guess I'm using the central store?

Should I place them in here on our DC? \\***********\SYSVOL\***********\Policies\policydefinitions Or what is the proper way of importing new admin templates? Thanks for any assistance!

Thanks for the insight.

In one of our classrooms we have a projector that looks best at output 1024*768 and the new computer has an HD monitor that has a native resolution of 1920*1080. I'm looking for recommendations on how to quickly switch resolutions back and forth. I have tried QRes, and it switches one way, but then when I use the script to switch back to 1920*1080 qres reports an unsupported resolution. Using a StarTech VGA splitter. Any help is appreciated!!! Thanks and Happy New Year!

Thanks! I figured this out like 15 minutes after I posted... I like the "don't panic." I think that all of us shouldn't panic... ever, there would be less stress. (But we don't live in a utopia now do we. )

Take a look at the screenshot, I am missing templates under this location. All I see is Office. How do I get the old ones back? Thanks, R

By registering the image do you mean letting is activate with KMS? I just figure it would be ok to sysprep after making the changes (even if the image is 200 days old - ha!). I usually complete a sysprep generalize and handle the unattend with WDS. But yes, I agree that just rebuilding the image is good too.

Any suggestions for a non-hyper-v environment? Do you know off hand if when you image a non sysprepped image, when you restore it 200 days later if it still the "same" in regards to licensing? I am using volume media and not entering a product key because I use KMS in the district. I am using WDS in the end.

How are some of you sealing your "master" image before the sysprep process? (So that you can restore that image and then sysprep again with needed changes further down the road?) Usually I image with clonezilla before sysprepping and then restore that image some days later if I need to make any changes. Any disadvantages to this?

I reposted in OS Deployment.

Has anyone noticed that the magnifying icon is missing from the "see more results" link when searching for a program while working in audit mode when preparing an image for deployment? I hope I'm not the only one. It also looks as if you sysprep from audit mode and copy profile the magnifying icon is missing in new user profiles as well. Any insight is appreciated. This is driving me bonkers. I have always customized my images in audit mode...