MRaybone

Hi I have a working Win10 (1703) deployment but the internet-wide recognised method of importing a start menu using Import-StartLayout (powershell) is failing with an access denied error to c:\users\default\appdata\local\microsoft\windows\shell\layoutmodifications.xml Now that file doesn't even exist but no matter what I do (local admin, UAC, etc etc) I cannot get the command to write to that location Any ideas? Cheers, MRaybone

Hello, I'm at a bit of a loss. Previously, I have installed Windows 7, customised it, run a simple MDT task sequence to capture the image where it is sysprepped and all was good. Is there a definitive way to do this with Windows 10? I just want to install Windows 10, install a few applications, then run a sysprep and capture task sequence. That's all, merely that. Is there any way this is possible without the process erroring horrifically? I can't grasp how this is suddenly so difficult, with so little quality information available anywhere. Help would be most gratefully received. Cheers, MRaybone.

Hello, I've set up VAMT 3 and would like to use a remote SQL database. Not difficult, however our SQL instance is clustered. This presents a new challenge, which I think I have a solution to, but to get there I need to be able to manually change the connection string that VAMT uses. I can only assume it's stored within the .MSC file some where/how. Is this possible? Does anyone know how to achieve this change? Cheers! MRaybone.

Sorry for the mini rant - I sorted the capture thing. I had added JoinDomain= to cs.ini.

Do I need separate Deployment Shares for building and capturing???

thadkew, Thanks for the information - the steps on customising Start and Taskbar look very useful! Not sure if I'll incorporate updates into the build. We use a 3rd party solution to patch - DesktopCentral. SCCM is great but too big for our organisation. I may just leave it to bake afterwards. Still not sure if my MDT Image Capture TS is working properly. Doesn't seem to want to restart the Win10 system after I've run it. Not sure what it's doing, but it might be skipping past the capture section. The whole SkipCapture=NO thing in the cs.ini is a bit of a mystery to me. This very same capture TS was working fine on Win7 systems last week.

Ok, thanks for your reply! From what I've attempted, and subsequently read, sysprepping Windows 10 AFTER a system has been on the internet and updated, is pretty much a no no. Seems the updated apps or something break sysprep. Is it just as simple as leaving the system off the internet totally, customising applications and sysprepping as normal? Our images are quite simple, just a few applications - Office 2016, Adobe Reader, Flash, Java, a password manager, that kind of thing. A customised Start Menu, taskbar and desktop would be great. We already do this for our Windows 7 images, but the process I use to customise the default user profile, I believe, is not valid in Windows 10. We leave our images running as VMs so they're patched via a 3rd party solution, and re-image them periodically. Guessing this isn't going to work for Windows 10 if updating breaks sysprep? Not too keen on provisioning applications and handling them in the TS, because the ones we do install are updated very frequently, and Office 2016/365 is basically an utter nightmare to deploy.

Hello! I have MDT image captures and TS deployments for Windows 7 and 8.1. It's pretty simple - I install an OS, customize it, run the litetouch script which syspreps and boots me into image capture. I capture image, import it into MDT and that image is deployable. Easy. Not for WIndows 10 - I'm at a complete loss. It seems many forums and blogs have various ways for me to mess with reams of powershell, vbscript, secret admin audit modes etc. I'd just like to customize - mainly software installations, I really don't care about the Start Menu - and then sysprep/capture in order to be able to deploy it via booting into MDT using WDS. Is that so hard? Any help appreciated! Cheers, M.

It appears I have solved the problem, unfortunately there are several things that I changed so one, all, or a combination of them might be the solution. For the benefit of all those Googlers out there... - Prior to image capture, I reset the Windows rearm count via the recovery console using this fairly well documented method: http://www.daniel-mitchell.com/blog/reset-windows-7-rearm-count/ - I pretty much reverted the Deployment Share Rules to default (not so sure this has any impact). - I copied a Task Sequence that I knew had worked previously. That combination resulted in deployment joy.

Hi all, I've recently taken over our WDS/MDT arrangement and have been creating and deploying images nicely. However I've come across an image which required some updates, and, upon capturing it, subsequent deployments no longer complete. Instead of logging on after the deployment, renaming the machine and adding it to the domain as per the final stages of the TS, it just does nothing and sits at the CTRL+ALT+DEL screen. I'm at a loss as to what is going on. Cheers, MRaybone.

Peter, wow, that's hardcore, but very cool. Thank you!

Hi all, What are the implications of taking a central site which has multiple primaries, and making that a child of a new central site? Forget about why I would want to do this, but what exactly would happen? Would things continue to operate as normal? Would the packages, queries, advertisements, collections etc on the current central site copy up to the new one? Cheers, MRaybone.

Also, if I change a client by using an HTA frontend tool (the ConfigMgr Client Troubleshooter), for example changing the assigned site or doing an auto discover site which results in a different site being assigned, is there anything I need to do to get these changes reflected in the SCCM console? Can I force this update? Cheers!

Hi all, We've had an issue here where clients were being assigned to the wrong SCCM site as there was a misconfiguration in our AD Sites & Services, and I'm using AD site boundaries. This has recently been rectified, but will clients, once they get their updated AD site, automatically reflect this change and get reassigned to the correct SCCM site? If not, what's the best way to go about getting clients to point in the right direction? Cheers, MRaybone.

In the SCCM console... Site Management -> [your site] -> Site Settings -> Addresses Right click Addresses -> New -> Standard Sender Address Select the site's site code in Destination Site Code, or type in the 3 letter site code if it isn't there. Enter the server name under Site Server Name. Configure your Schedule and Rate Limits if required. Finish!