Harmen1966

Hi. We’re having a problem with the regional and locale setting in Windows 10 1709, we’re creating a reference image with MDT 2013 on an US 2012 R2 server but we’re using the Dutch ISO of Windows 10 1709. After creating and deploying this image the language is Dutch however the regional and locale settings are US, is there a simple way to set this to Dutch, or should I install the Dutch language pack to set this straight. TIA, Harmen

It's an WMI issue, create a batch file and run it as Administrator, put the text lines in it; @echo off sc config winmgmt start= disabled net stop winmgmt /y %systemdrive% cd %windir%\system32\wbem for /f %%s in (‘dir /b *.dll’) do regsvr32 /s %%s wmiprvse /regserver winmgmt /regserver sc config winmgmt start= auto net start winmgmt for /f %%s in (‘dir /s /b *.mof *.mfl’) do mofcomp %%s Restart the server when finished. Well that doesn't do the trick after several minutes I got the error again.

This solution worked for me but I had troubles to editing the InstallUtil.exe.config so I ran installtakeownership form the zip file, do the job and then removetakeownership then the msi installed like a charm and the SMS_NOTIFICATION_SERVER went up and running. Harmen TakeOwnership.zip

Yes we have a remote DB server.

Many, many thanks for this great guide it helped me a lot to upgrade our SCCM envoirment, one hint after the SP2 upgrade also restart the DB server I had no site components, but restarting the DB server the're all back pfiew! Harmen

Can I use the technet eval version but with our own serial number, because I can not download the original version from MSDN. Thanks. Harmen

Thank you.

Excellent post thanks. Question can I use this document without the MDT upgrade because we don't use MDT. TIA, Harmen

Yes I know and I will do that but I was wondering why stopped the updateing of my machines, I want to find a correct solution. It seems it happened on the x86 image not the x64 image, something to do with memory. Net stop wuauserv, Sc config wuauserv type= own, Net start wuauserv kick off some updates but not all

@Jaybone Thanks for the reply. 1. The problem of deploying updates is after the OSD, the ADR rule with the Windows Updates won't run. 2. I've some WU in the image when created the image, but after a few months the updates grow so the ADR rule had to push them to the workstations and that stucks. which logs should I retrace in the correct order to identify the problem

Hi. I've followed the instructions to setup ADR and for months it worked like a charm but something got wrong and I can't figure it out what it would be. The ADR is applied to the collection but after an OSD to the computer not all Office and Windows updates are installed, searched the logs but I don't exactly wich order to troubleshoot. If i manually download the updates there is a whole list op 57 updates. TIA. Harmen

Problem solved by enable IPv6 on the DP server I was forgotten to enable it after testeing another issue.

Yes with various models it's the same, the WinPE4 boot images downloads the drivers fast but the WinPE5 (after the R2 upgrade) are extremly slow, even when i'm not using driver packages but auto apply drivers instead. Yes the machine is joined to the domain but after the install configmgr client step no other step wil be run, in my case it's activate Windows, yes if I logon I see that the SCCM client is the latest one so the TS uses the newest client. Update; smsts.log file attached. smsts-20140118-035240.log

Hi, After upgrading from SCCM 2012 sp1 to 2012 R2 i've got two major problems; the first one is installing drivers step from driver package is extremly slow (but when using the WinPE4 boot images this step works fine) second one is every step after the "install configmgr client" step will not be run KB2905002 is installed and I used the new boot images created by SCCM 2012 R2, update boot images on DP after apply the hotfix. Update: auto apply drivers is also very slow with the new boot images. Any help will be appreciated

update: I’ve waited after patch Tuesday and find out according to the MS security advisory notification that our Windows 7 clients perfectly updated with the updates mentioned in this document. But when I look at our Windows 2008 R2 servers updated with WSUS and our test server as my test server for Windows updates thru SCCM then I see a difference of three updates. The updates that are not installed are on my test server are 2868725, 2862152 and 2900986 they were perfectly installed on the other 2008 R2 servers.