Lagamorph

Ah right, so we wouldn't need to change the environment? As long as the original SUP can sync with Microsoft Update (which it can as we've been using it for a while), the new SUP will automatically sync from that one directly and doesn't require internet access. Is that correct? To store updates will it just use the WSUS local storage that was configured during the installation of the WSUS role? The location specified here,

Ahh right. The thing is that configuration menu is for the SUPs to sync from Microsoft Update, but we don't want this particular SUP to do that as it wont have internet access. We want it to synchronise from one of the other SUPs.

I can open that menu yes. So if those settings are configured then it means that they'll override all SUP settings for the entire site and so we can't/don't need to configure options for individual Software Update Points? So therefore we don't even see the options when installing the role to a new server?

I experienced a similar issue a while ago, but it was due to my using a Windows image that had been created from a Build & Capture, so already had the client installed, but I had put it into the task sequence to install the client again then do things like application installation and windows updates. If you try plugging in a new/fresh windows image ripped straight from an ISO again do you still get the same issue?

Hi guys, We've deployed a new server into our SCCM infrastructure which currently has the following roles installed, Component Server Distribution Point Management Point Site System And we would like to add it as a Software Update Point for some specific servers. When we run the wizard to add the Software Update Point role though, we're missing a lot of the options that are supposed to be present, such as Synchronization Source. The wizard only gives us the below, When what we believe we should be getting is something more like this, We've installed SQL and the WSUS role on the server, so seem to have all the pre-requisites. If we complete the wizard then it seems to complete successfully, but we can't seem to configure any of the SUP role options for the server. The SCCM version is R2 SP1. Site version is 5.00.8239.1000 and Console Version is 5.0.8239.1206 Does anyone know why these options might be missing? Is it possible we have some services on the server not running that are required? Or is there a pre-requisite that's been missed?

Thank you!! Yep, that update did it. As soon as I uninstalled it and rebooted, I could install Roles & Features via the Wizard again. I'll need to get it disabled in SCCM from the looks of things to prevent it being deployed in future. I'm not sure how this is breaking. .Net 4 is being installed during SCCM deployment by the Add Roles & Features wizard, then windows updates applied from SCCM automatically. Could be that one of my deployed applications is updating .Net Framework to 4.6, then the update is being applied from SCCM I suppose.

I was wondering if anyone might be able to assist with an unusual issue I'm having. We've deployed some Windows Server 2012R2 machines from SCCM and everything is working correctly, except the Add Roles and Features wizard. For some reason, whenever we try to install absolutely any role/feature via the wizard, it fails immediately with no error messages. At first I was wondering if it was an issue with the source path or something, however adding roles/features through Powershell commands works perfectly without specifying an alternate source. For example, if I try to add the Failover Clustering feature via the Wizard, it immediately fails. However, if I run the below in an administrative Powershell prompt, Install-WindowsFeature -Name Failover-Clustering -IncludeManagementTools Then it works perfectly and the feature is installed. So does anyone know why the wizard might be failing?

You may be able to do it using a Powershell script that is run during the Task sequence, https://social.technet.microsoft.com/Forums/windowsserver/en-US/8e81ab93-5be5-4f61-b916-97e85b36921a/can-i-change-the-pagefile-location-via-powershell?forum=winserverpowershell

Have you tried changing "reg import license.reg" to "regedit.exe /s license.reg" ? (Don't forget to update your Distribution point after modifying the batch file)

Managed to find a solution to this. Incase anyone else runs into the same error, https://social.technet.microsoft.com/Forums/en-US/be2c05a0-620c-4b64-a82f-18ccc9f6cec5/apply-gpo-pack-offline-media-does-not-apply But to summarise, You need to edit the ZTIApplyGPOPack.wsf in the MDT Files. In the list of declared variables at the top of the script, add an additional variable, Dim LSDB Then, just before the "Run GPO Pack Script" section, add the following, '// Remove read only Attrib. from LocalSecurityDB.sdb LSDB = "Attrib -R " & oUtility.LocalRootPath & "\" & sGPOPackPath & "\LocalSecurityDB.sdb /S" oShell.Run LSDB,0 It appears that the problem is with the Security database being read-only when using an Offline ISO build, but not when using a Boot Image/PXE Boot. I've tested the script with both Offline ISO and Boot Image builds, and it works perfectly in both scenarios.

Don't suppose anyone has any ideas about this do they?

Hi all. I've created a task sequence that, when deployed from SCCM via a Boot image, works absolutely perfectly. Performs all my steps and then lastly applies a GPOPack placed in the Templates\GPOPacks folder of my MDT files. When I generate a Stand-alone media ISO from this task sequence however and run that through, everything works except for the GPO Pack not being applied. This is immediately obvious as no logon message is displayed after pressing Ctrl+Alt+Del and the account renaming carried out by the pack is not done. I've checked the smsts log file though and according to that the Apply GPO Pack stage has completed successfully with exit code 0, no errors, though it does complete in only 3 seconds which seems a little fast. Any ideas on what might be causing this strange behaviour?

Thanks guys! Exactly what I needed

Hi all. We've got some boot images that had various drivers injected into them, however the SCCM server has since been updated, meaning that the boot images can no longer be modified. This is no problem, as I don't want to modify them, however I do want to actually view what drivers have been added to the boot image, but I can'd do this as the Drivers tab is now missing for the older images. Is there any other way that I can view which drivers have been injected into the boot image? I know I can mount the .wim using DISM, but that's not really going to help me identify which of the drivers present in SCCM have been added in will it?

You could try putting the commands into a notepad file and saving it as "Install.cmd", then turning that into a Package, with the folder containing Install.cmd as the source folder. Then create a Standard Program in that package, specifying Install.cmd as the command line, and you can then configure that the Program can run whether a user is logged on or not, which will also put the Run mode to "Run with administrative rights". Then just install the package as part of your task sequence at the point you were putting the command line entries.

They were the same, en-GB and 809 keyboard code, same with the windowsPE phase. I've done some further reading and found one post on Technet that suggested only changing the SystemLocale, UserLocale and UILanguageFallback to en-GB, leaving everything else (such as UILanguage and InputLocale) as the default en-US in all phases of the unattend.xml. I've given this a try and the build does appear to have now been successful. Going to do a few more tests, including a build with the Enterprise index, but so far so good. It looks like the cause of the issue may have been a conflict in the unattend.xml between the languages I was trying to set and the language of the base image after all. I'm also going to try changing the InputLocale but leave the UILanguage alone at en-US, since the deployed image still has american keyboard layout and date formatting. If that causes the selection screen to come back up again though, I may have to admit defeat on that one for the time being and perhaps look to have those set by GPO. Thanks very much, looks like you were right about the unattend.xml being the cause of the problem

Hi, I've located the Specialize step in my Unattend.xml, however within that I have specified the settings in the "Microsoft-Windows-International-Core" area, which is the only place I can find to configure location options that would seem to influence this. Below is the specialize step from my xml file, <settings pass="specialize"> <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"> <Identification> <Credentials> <Username> </Username> <Domain> </Domain> <Password> </Password> </Credentials> <JoinDomain> </JoinDomain> <JoinWorkgroup> </JoinWorkgroup> <MachineObjectOU> </MachineObjectOU> </Identification> </component> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"> <ComputerName> </ComputerName> <ProductKey> </ProductKey> <RegisteredOrganization> </RegisteredOrganization> <RegisteredOwner> </RegisteredOwner> <DoNotCleanTaskBar>true</DoNotCleanTaskBar> <TimeZone>Pacific Standard Time</TimeZone> </component> <component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Home_Page>http://www.microsoft.com/</Home_Page> <DisableWelcomePage>true</DisableWelcomePage> <DisableFirstRunWizard>false</DisableFirstRunWizard> </component> <component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Description>EnableAdmin</Description> <Order>1</Order> <Path>cmd /c net user Administrator /active:yes</Path> </RunSynchronousCommand> <RunSynchronousCommand wcm:action="add"> <Description>UnfilterAdministratorToken</Description> <Order>2</Order> <Path>cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v FilterAdministratorToken /t REG_DWORD /d 0 /f</Path> </RunSynchronousCommand> <RunSynchronousCommand wcm:action="add"> <Description>disable user account page</Description> <Order>3</Order> <Path>reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE /v UnattendCreatedUser /t REG_DWORD /d 1 /f</Path> </RunSynchronousCommand> </RunSynchronous> </component> <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <InputLocale>0809:00000809</InputLocale> <SystemLocale>en-GB</SystemLocale> <UILanguage>en-GB</UILanguage> <UserLocale>en-GB</UserLocale> </component> <component name="Microsoft-Windows-TapiSetup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <TapiConfigured>0</TapiConfigured> <TapiUnattendLocation> <AreaCode>""</AreaCode> <CountryOrRegion>1</CountryOrRegion> <LongDistanceAccess>9</LongDistanceAccess> <OutsideAccess>9</OutsideAccess> <PulseOrToneDialing>1</PulseOrToneDialing> <DisableCallWaiting>""</DisableCallWaiting> <InternationalCarrierCode>""</InternationalCarrierCode> <LongDistanceCarrierCode>""</LongDistanceCarrierCode> <Name>Default</Name> </TapiUnattendLocation> </component> <component name="Microsoft-Windows-SystemRestore-Main" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DisableSR>1</DisableSR> </component> </settings> Is there something there that's missing? Or could the issue be down to me setting en-GB in everything even though I'm using an en-US image?

Hi all, I've managed to resolve language pack problems I've been having with 2008R2 and 2012R2 deployments, but just cannot get past the issues I'm having when attempting to deploy 2008 SP2 (x86). All attempts to install the language packs during the task sequence ended in failure (including trying to use a DISM command during the task sequence), and even attempting to manually install the language pack on a deployed image also failed (the language pack was reported as compatible, the installation just failed with a generic error and no further information). Eventually I used DISM to add the language pack package to the image offline before deployment, and this completed successfully. However, now upon attempting any deployment using the image, I'm presented with the below screen, If I select English and then hit next, I get a "Thank you" screen and also have to click 'Start', before the deployment then proceeds as normal. I've got the below Customsettings.ini configured to try and skip this, but to no effect, [settings] Priority=Default Properties=MyCustomProperty [Default] OSInstall=Y SkipCapture=YES SkipAdminPassword=NO SkipProductKey=YES SkipLocaleSelection=YES SystemLocale:en-gb InputLocale:en-gb KeyboardLocale=0809:00000809 UserLocale=en-GB UILanguage=en-GB SkipTimeZone=YES TimeZoneName=GMT Standard Time SkipSummary=Yes The part in bold is what I have added in addition to the default Customsettings.ini I think the reason for this is because I'm using an image that's originally en-us, then have applied a German Language pack, and am then trying to configure en-GB Timezone/keyboard/language. However even if I use the original customsettings.ini file, so not attempting to configure en-GB and just leaving the en-US defaults alone, I still get the same issue and the deployment stops on that screen. I have attempted to use DISM on the image to run /Set-SKUIntlDefaults:en-gb but this ends in a failure that DISM isn't supported on the target image, likely because it's 2008SP2 x86. If anyone has any suggestions I'd very much love to hear them

Sorry to bump this, but encountering a new problem along the same route. I've successfully applied this process to Server 2008R2 to apply the language pack, but it doesn't appear to have been successful for 2008 x86 when I've followed the same steps. I've downloaded the 2008 x86 MUI, then used the above steps to apply the language pack in my task sequence, but the OS still comes up in the non-English language. I've also configured my Customsettings.ini with the following, SkipLocaleSelection=YES KeyboardLocale=0809:00000809 UserLocale=en-GB UILanguage=en-GB SkipTimeZone=YES TimeZoneName=GMT Standard Time And my Unattend.xml with the following, <SetupUILanguage> <UILanguage>en-GB</UILanguage> </SetupUILanguage> <InputLocale>0809:00000809</InputLocale> <SystemLocale>en-GB</SystemLocale> <UILanguage>en-GB</UILanguage> <UserLocale>en-GB</UserLocale> But I still get the non-English language from the base image. Is the process for applying language packs in 2008 different to R2?

Sounds like the scheduling may have been incorrectly set. I've found that when deploying new sequences they can take a while to become available as even when selecting "As soon as possible" during the sequence deployment, it then defaults to at a specific time (which is usually the current time) and the "Soon as possible" option becomes greyed out. It seems that the boot image uses a different time zone that is sometime in the future to my SCCM server. My general way around it is, after creating the task sequence and deploying it, go into the properties of the deployment and then the scheduling tab, then change the date to some time in the past. If you try to do this during the deployment it wont go more than 1 minute in the past, but in the deployment properties it can be any time.

Hi all, As part of some of the SCCM things I'm working on (whilst also learning), I've got a requirement to deploy some Windows Server 2003 (I know I know, old and unsupported, but the decision isn't up to me) servers, however I'm having some trouble adding the OS into SCCM 2012 for deployment. I have our 2003 ISO, however it doesn't have a WIM file as later versions of Windows have, just the Setup package and lots of other files. I've had a look through some of the guides and it looks like this was doable in SCCM 2007 from the guides on that, using the "Operating System Install Package" section, however 2012 doesn't have this, only an "Operating System Upgrade Packages" section. I can add a package here, and under the details tab it does appear to be picking this up as an OS, however this package isn't available when attempting to create a Build & Capture task sequence Are there additional steps required to deploy 2003 from SCCM 2012? Or is this simply not possible/not supported anymore? I was thinking I might need to mount the Iso onto a VM and just do a manual installation, then run a purely capture task sequence, though the wizards in SCCM only seem to allow for the creation of a Build & Capture sequence, not a pure capture sequence, at least not that I can find anyway.

Ahh I see. I managed to figure out a way to get it working without the need for an install.bat file. I just needed to create a package without a program, then use the MDT task sequence option to install a language pack offline, pointing to that package. Did a test deployment and appears to have worked flawlessly Avoids the need to copy over the language pack files first and then install using a command line. I'll get the hang of SCCM eventually I'm sure!

Hi all, I'm still very new to SCCM, but am currently working on some task sequences in SCCM 2012 SP2 to deploy Windows Server Operating Systems. Now I've used the excellent guides here to get to grips with creating some task sequences to perform tasks such as Build & Capture a reference image, and installing/integrating MDT 2013 for additional functionality, however I've hit a stumbling block with what I'm trying to do now. Essentially the Windows server image that's being deployed is in one language, but I also need to install a language pack for another language onto it during the deployment. I have found this guide, http://www.windows-noob.com/forums/topic/3251-customising-windows-7-deployments-part-4/ , (though this is for Windows 7 and I'm deploying 2008 R2, the basic principles seem to be the same), however I'm stuck at this step, "create a System Center Configuration Manager package that contains one or more language packs". My question is, how do I do that? I can go into SCCM and create a package, specifying my source files (The folder containing the .cab file I've extracted from the MUI ISO), however I get stuck when it's trying to create the program. I have no idea what I'm supposed to enter into the command line section. I'm assuming this would be an install.bat, but what should the contents of that install.bat be? I'll be going for an unattended/offline install of the language pack during the Deployment task sequence. Would the install.bat be something along the lines of, lpksetup.exe /i en-US /r /s /p %SYSTEMDRIVE%\LangPack Sorry if these are basic questions, but I'm very much learning SCCM as I go.