Sysprepping Windows 10

[Tefters]

So I did this:

 

Built image on workgroup from SCCM, with administrator password set

Logged in as administrator

Ran Get-AppxPackage *3d* | Remove-AppxPackage to delete all the packages I di not want

Ran Remove-AppxProvisionedPackage -PackageName Microsoft.Zune.xxx333.444.xxxx (etc) for each package I didn't want.

 

And Syspreped

 

Test now is what will a new user get when they sign in.

 

Exact same test I'm doing now, I guarantee that remove-provisionedappxpackagrs stops new users from getting the apps, it's more the question of will it sysprep after that as it hasn't previously but doing it in specific order.

[snagrat]

Worked for me (although I forgot to take some out I don't want!)

[Ephelyon]

What we're considering doing is moving from Start Menu shortcuts to Desktop shortcuts.

 

You can remove the "All Apps" button via GPO and then move your shortcut folders to the Desktop. That means users won't get to see all the extra gumph anyway, and it also deals with the issue of not being able to have shortcuts in sub-folders on the new Start Menu.

[JRowley]

Which version of SCCM are you running?

 

It seems that 2012 R2 SP1 doesn't fully support Windows 10 images (for example you cannot modify W10 boot images in SCCM), that's not coming until SCCM 2016.

Ignore me completely.

Edited August 6, 2015 by JRowley

[Arthur]

for example you cannot modify W10 boot images in SCCM

Doesn't that only apply to older boot images?

 

NOTE: After you update the ADK on your site server to Windows 10 ADK you will not be able to edit older boot images in console you will have to manually edit them outside with dism if still needed. Good news is the Windows 10 ADK supports Windows 7 and later so there should be little need to keep older boot images around.

 

http://blogs.technet.com/b/brandonlinton/archive/2015/07/30/windows-10-adk-boot-image-updates-for-configuration-manager.aspx

 

Any existing Windows PE 3.1 or Windows PE 5 boot images can still be used, but are no longer customizable from the Configuration Manager console. You can create new boot images which will now be using Windows PE 10. Windows PE 10 boot images support deployments of Windows 7 through Windows 10.

 

http://blogs.technet.com/b/configmgrteam/archive/2015/08/05/windows-10-adk-and-configuration-manager.aspx

[JRowley]

Clearly the summer sun has done something to my head *looks outside at the rain*, I haven't rebooted our SCCM server since installing the Windows 10 ADK which probably explains why I'm getting a different experience.

[denzal2k4]

Right so, I had pinned Internet explorer and Adobe Reader (amongst other things) to start, exported start layout, set gpo to deploy, all good so far, start menu etc deployed but the links for IE and adobe are pointing at MY roaming appdata, so other users don't get given those shortcuts. Any ideas how to get round this?? All the other custom items show up OK....

[Arthur]

Any ideas how to get round this?

Modify the paths in the StartLayout XML file?

[Wolverine-911]

Has anyone managed to sysprep yet with the built in apps removed by any chance?

[denzal2k4]

I've just left them in, they don't seem to launch as students anyway.

[Arthur]

The following might catch a few people out who are using SCCM to capture images instead of MDT.

 

MDT UberBug10 – Win10 OS Capture using SCCM is not supported

 

Someone asked about running sysprep.exe under the system context, and someone else mentioned that execution of the sysprep.exe is *not* supported in the system context for Windows 10. I suspect this has to do with all the new fancy Metro/Modern/Universal apps that have plenty of junk that needs to be cleaned up by sysprep.

 

By the way, it's not a bug. It's a feature.

 

https://twitter.com/jarwidmark/status/636976440714612736

 

http://i.imgur.com/dyD4ugS.png

[Deniise]

Has anyone managed to modify the start menu, using CopyProfile.xml and sysprepping the reference image? .. Been trying for days to modify the start menu by clearing all default tiles and pinning a few Office and utilities tiles (12 medium tiles in 2 groups, in 3 columns and 2 rows). I have a very basic copyprofile.xml file (containing copyprofile = true option) in my Sysprep folder which is then used in a generalize /oobe /shutdown command prior to capturing the image. I deploy the image in my environment using an SCCM 2012 R2 CU1 task sequence with unattend file set to copyprofile.

 

All customized profile settings are carried over onto new profiles after deployment but the start menu is all screwed up because the same tiles I chose are pinned, however they are not in the order (and groups) I put them in prior to capturing ... any clues, guys? Thanks

[Tefters]

Has anyone managed to modify the start menu, using CopyProfile.xml and sysprepping the reference image? .. Been trying for days to modify the start menu by clearing all default tiles and pinning a few Office and utilities tiles (12 medium tiles in 2 groups, in 3 columns and 2 rows). I have a very basic copyprofile.xml file (containing copyprofile = true option) in my Sysprep folder which is then used in a generalize /oobe /shutdown command prior to capturing the image. I deploy the image in my environment using an SCCM 2012 R2 CU1 task sequence with unattend file set to copyprofile.

 

All customized profile settings are carried over onto new profiles after deployment but the start menu is all screwed up because the same tiles I chose are pinned, however they are not in the order (and groups) I put them in prior to capturing ... any clues, guys? Thanks

 

The copyprofile in Windows 10 has been broken since early beta and has been reported a lot of times to Microsoft and is awaiting a patch however I wouldn't hold your breathe for anytime soon.

 

There is the Group Policy custom start menu but have yet to play around with it as I put my Windows 10 deployment on hold due to the sysprep remove-appx original issue eating 3 days early on to then get patched a week later buy at that point had already thrown in the towel in favour of updating all app versions.

 

There are a few posts lurking around regarding the Windows 10 custom start menu GP and people having problems so it might not be working properly yet either.

[Deniise]

At this stage, I'm actually considering deploying our machines with the default start menu layout since I'm not excluding the possibility of bugs...However I have read about the group policy and I believe that this method is not 'supported' by Microsoft and being in an enterprise environment, I tend to steer clear from such configurations which don't originate from Technet/trusted sources (based on past experiences!).

[Tefters]

At this stage, I'm actually considering deploying our machines with the default start menu layout since I'm not excluding the possibility of bugs...However I have read about the group policy and I believe that this method is not 'supported' by Microsoft and being in an enterprise environment, I tend to steer clear from such configurations which don't originate from Technet/trusted sources (based on past experiences!).

 

Huh? The group policy custom start menu is a Microsoft Windows 10 group policy that was implemented with the new ADMX files therefore it is supported and advised by Microsoft.

 

You simply build a start menu, run an export command in powershell, chuck the xml output in a share (netlogon being a good example) and then implement the GP with the xml... It's not rocket science...

 

The caviet as said before is that it does not appear to work properly if you check other threads in this forum / do a quick Google and with the copyprofile being broken since Beta is a complete pile of poop.

 

Another class example of Windows 10 not being ready for enterprise.

 

However much I hate Windows 8.1 at least at the moment it works and until Microsoft sort out the configurations bugs and their lack of GP control for Windows 10 in general I won't push out an image.

 

Silly thins as well are annoying like offline servicing not working on Windows 10 in SCCM 2012 R2 SP1 so would have to keep opening the image and injecting updates and closing again...

[Arthur]

Silly things as well are annoying like offline servicing not working on Windows 10 in SCCM 2012 R2 SP1

That bug has already been fixed.

 

 

https://support.microsoft.com/en-us/kb/3089193

[Arthur]

Run capture image ISO fro SCCM and fail on sysprep

Using SCCM to capture your image probably explains why you are having so many problems...

 

https://keithga.wordpress.com/2015/08/27/mdt-uberbug10-win10-os-capture-using-sccm-is-not-supported/

 

Use the latest MDT (or wait for the re-release) and it should work better.

[Tefters]

That bug has already been fixed.

 

 

https://support.microsoft.com/en-us/kb/3089193

 

Cheers for this!, I haven't done my weekly blog reads yet.

 

As for the capture ISO bug I fixed that easily with a workaround as it was due to the Appx package and Appx provisioned package bug and then a week after I figured out a workaround they patch it anyways.

 

Andy

[Deniise]

Using SCCM to capture your image probably explains why you are having so many problems...

 

https://keithga.wordpress.com/2015/08/27/mdt-uberbug10-win10-os-capture-using-sccm-is-not-supported/

 

Use the latest MDT (or wait for the re-release) and it should work better.

Would you mind keeping us updated about your ticket with Microsoft please?

[Arthur]

Would you mind keeping us updated about your ticket with Microsoft please?

I don't have a ticket open with Microsoft?