Modify c:\users\default\ntuser.dat during the TS. Scripted. Automated. Repeatable. Easily tested. Portable. No evil manual work. Done.
J From: [email protected] [mailto:[email protected]] On Behalf Of Mote, Todd Sent: Monday, June 17, 2013 3:08 PM To: [email protected] Subject: [MDT-OSD] RE: Windows Store failing to start after imaging Agree, but then there's posts like this: http://blogs.technet.com/b/askcore/archive/2010/07/28/customizing-default-users-profile-using-copyprofile.aspx - The best part from this one, sadness for those of us that use ConfigMgr to build and capture: * Use of CopyProfile with ConfigMgr * Since ConfigMgr runs in the system context when building an image it is not possible to use it to copy customizations to default user * One option is to use Microsoft Deployment Toolkit 2010 to build your reference image and then deploy that image with ConfigMgr And then there's this, which is much more recent, and makes CopyProfile seem pedestrian and easy! :D http://technet.microsoft.com/en-us/library/hh825135.aspx Sigh. Why can't this process be easier? Just a little? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Monday, June 17, 2013 4:57 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: Windows Store failing to start after imaging CopyProfile = evil From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Monday, June 17, 2013 12:01 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: Windows Store failing to start after imaging No, we actually had to take that line out. We were using it initially to configure the default users profile. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Iacaruso, Mike Sent: Monday, June 17, 2013 2:38 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: Windows Store failing to start after imaging Daniel, so all you did was add the copyprofile line to the unattend.xml file? Mike Iacaruso Enterprise Desktop Engineer Office of Technology Services Towson University 410-704-3965 [email protected]<mailto:[email protected]> From: [email protected]<mailto:[email protected]> [mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of Daniel Ratliff Sent: Monday, June 17, 2013 1:41 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: Windows Store failing to start after imaging Yes!! I fought with this issue for weeks, had calls open with Microsoft and found the culprit to be two things: 1. <copyprofile>True</copeprofile> in out unattend.xml, this copies the SYSTEM profile in Window 8 and by default the SYSTEM profile does not have any access to store apps 2. AppLocker/Software Restriction policies leftover from Win7 GPOs were restricting apps from launching. We are using ConfigMgr/MDT integrated and changing the two above items resolved our issues! Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Iacaruso, Mike Sent: Monday, June 17, 2013 1:24 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] Windows Store failing to start after imaging I am having a strange issue with the Windows Store after deploying a MDT 2012 Windows 8 image. I deploy the image and after logging into the system the I cannot get the Windows Store to start. The store just opens and then closes. I did not update any of the pre-installed Windows Metro apps before syspreping the system. Did anyone have a similar issue with the Store? Mike Iacaruso Enterprise Desktop Engineer Office of Technology Services Towson University 410-704-3965 [email protected]<mailto:[email protected]> The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
