If I delete a computer from SCCM, the computer has no issues PXE booting.  

I have yet to find a collection that I can deploy a TS to and get it to PXE boot.  If I force it (booting from flash drive), no task sequences are available.  I'd post some screenshots but this account is new.  

At the moment I'm using a query based collection that is the default query "Select * from SMS_R_System" but other collection subsets have similar results.  It's possible a direct rule works (I need to try it again) but isn't a solution.  The machine I'm trying to PXE boot shows up in the collection.  

The monitoring section says that most of the machines are "Requirements not met" "Program rejected (wrong platform) which I presume to mean they are not currently in a WinPE environment or having been booted from pxe/media.  Perhaps that is why WDS isn't sending them PXE data and why they show up as having no sequences available.  

Is it possible to do this without also publishing the TS to the software center?

Have a 2012 client, and we are attempting a very basic task sequence that requests the state store, does a a capture, and releases the state store. This is intended for an in-place migration, so no computer association has been created.

However, we are getting odd failures.

Client1 resides at IP a.b.c.d, and that subnet is listed in the 'USMT test boundary' boundary group, as well as the range a.b.c.1-a.b.c.254. The Boundary group is associated with a Desktop based DP, as well as our dedicated SMP server.

When the request state store runs, it fails and this is what we find is smsts.log

Command line: "osdsmpclient.exe" /capture OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
Client joined to the XYZ domain. OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
Client is a member of the Columbus site. OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
DhcpGetOriginalSubnetMask entry point not supported. OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
Begin checking Alternate Network Configuration OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
Finished checking Alternate Network Configuration OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
Adapter {4CCABA30-E631-45C2-A9A6-55EA390F718A} is DHCP enabled. Checking quarantine status. OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
Loading client certificates. OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
Default CSP is Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype) OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
Default CSP Type is 24 OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
Setting the client certificate provider to Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype). OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
Successfully set the client certificate provider to Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype) OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
Successfully set the client certificate provider to Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype) OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
Requesting a list of available state migration points from the management point. OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
Initializing HTTP transport. OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
cannot create a certificate context from the given encoded string OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
Set authenticator in transport OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
Sending request to MP MP.domain.com. OSDSMPClient 4/12/2013 10:12:19 AM 3160 (0x0C58)
signature varification failed OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
signature varification failed OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
signature varification failed OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
signature varification failed OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
Received 46974 byte response. OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
Retrieving SMP list.. OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
SMP Location Info = <SMPLocationInfo><Sites><Site><SMPSite SiteCode="sitecode" MasterSiteCode="sitecode" SiteLocality="REMOTE"><LocationRecords><LocationRecord><ADSite Name="Columbus"/><IPSubnets><IPSubnet Address="F.G.H.0 -->not the IP subnet of the client"/><IPSubnet Address=""/></IPSubnets><ServerName>http://SMPServer.domain.com</ServerName></LocationRecord></LocationRecords></SMPSite></Site></Sites></SMPLocationInfo> OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
DHCP entry points already initialized. OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
Begin checking Alternate Network Configuration OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
Finished checking Alternate Network Configuration OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
Adapter {4CCABA30-E631-45C2-A9A6-55EA390F718A} is DHCP enabled. Checking quarantine status. OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
Number of local SMP's = 0 OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
Retrieving SMP list succeeded OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
Looking for UsersList OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
User List is empty in MigrationInfo from MP. OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
Successfully processed response from MP. OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
Contacting available state migration points to service capture request OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
No state migration points are available to service request. OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
ExecuteCaptureRequestSMP failed (0x80004005). OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
ExecuteCaptureRequest failed (0x80004005). OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
OSDSMPClient finished: 0x00004005 OSDSMPClient 4/12/2013 10:12:20 AM 3160 (0x0C58)
Process completed with exit code 16389 TSManager 4/12/2013 10:12:20 AM 4848 (0x12F0)

What is even more counfounding is that if I add a new boundary group with just this subnet, and associate it only with our SMP, the task sequence will fail to run, stating 'The software could not be found on any servers at this time', when I know the boundary is listed in both boundary groups. Removing this second boundary group reverts the issue back to the error about not finding a SMP.

Thoughts?

Will

We just created the new Boot file and we are using site based media ,now users are facing this error "An error occurred while retrieving policy for this computer". TS is working fine in our labs computers but for the Local IT it got failed with the above error .I have checked the certificate those are ok .MP is working fine , I didn't checked the IIS log on the MP yet .

Is there anything I can do in IIS manager to resolve this issue ?

I recently have been getting socket and winhttp failures in our task sequences. I'm able to ping the FQDN of the MP and also nslookup to resolve dns so that seems to be ok. Certs also looks fine.

I attached log file, but I replaced domain names with xxxxx.xxxx.com

https://drive.google.com/open?id=1To0tqpBr4y4ZLlUWLHIh10jbiMkOjJPG

I will be very happy with any help.

I am trying to restore the user data with USMT hard link. I am able to capture the user state to c:\userstate, but while restore its failing with below error. As per smsts.log its connecting to the right store (c:\userstate)

error from loadstate.log

2019-11-14 06:57:16, Info                  [0x000000] Command line: C:\_SMSTaskSequence\Packages\xxx003F6\amd64\loadstate.exe C:\UserState /ue:machinename\* /c /l:C:\WINDOWS\CCM\Logs\SMSTSLog\loadstate.log /progress:C:\WINDOWS\CCM\Logs\SMSTSLog\loadstateprogress.log /i:C:\_SMSTaskSequence\Packages\xxX003F6\amd64\MigApp.xml /i:C:\_SMSTaskSequence\Packages\xxX003F6\amd64\Migdocs.xml
2019-11-14 06:57:16, Info                  [0x000000] Failed.[gle=0x00000006]
2019-11-14 06:57:16, Info                  [0x000000]   An error occurred processing the command line.
  Invalid store path; check the store parameter and/or file system permissions[gle=0x00000006]
2019-11-14 06:57:16, Info                  [0x000000] USMT Completed at 2019/11/14:06:57:16.422[gle=0x00000006]
2019-11-14 06:57:16, Info                  [0x000000] ----------------------------------- USMT ERROR SUMMARY -----------------------------------[gle=0x00000006]
2019-11-14 06:57:16, Info                  [0x000000] * USMT error code 27: [gle=0x00000006]
2019-11-14 06:57:16, Info                  [0x000000] +-----------------------------------------------------------------------------------------[gle=0x00000006]
2019-11-14 06:57:16, Info                  [0x000000] | An error occurred processing the command line.[gle=0x00000006]
2019-11-14 06:57:16, Info                  [0x000000] | Invalid store path; check the store parameter and/or file system permissions[gle=0x00000006]

Midhun.PS

while installing python3.7.5(64-bit) to my windows 7.

It said: setup failed;0x80070661-this installation package isn't supported by this processor type.

I have a working bare metal task sequence I was using to install 1709 x64 in our environment. I copied my master task sequence and changed the OSD to the Win10 1809 x64 using the newest ISO from the Volume Licensing Center. When trying to simply use the image wim in the ISO, the image states it worked. SMSTS shows exit code 0 and success, but when loading the machine, its stuck in a reboot loop stating it needs to install an update but not naming the update on the screen. Instead, it will simply get stuck. I tried to F8 into safe mode, but it states it will not load the safe mode until it finished installing Win 10. I can get to the troubleshooting and the command prompt, but I'm not even sure what log to look at as I can't use Event Viewer in this particular instance. I tried using DISM and injecting the latest Cumulative update I could find into the Win 10 ISO and it did the same thing still. Then I tried to do a build and Capture to try pulling the new Image from there and got a WMI error that will not allow me to edit the task sequence, even after rebuilding it 4 times.

Potential side issues that could be related, but I don't know anymore: 

We have had an issue with some files seeming to disappear(like drivers all the sudden not being distributed and our office files disappearing from our Source share) so its possible something is missing, but I've redownloaded and rebuilt the ISO repeatedly. We also had an issue with our primary appearing to expired updates in WSUS and it was not allowing our Upgrade servicing to work until we unexpired these updates.

I'm at a loss and pulling my hair out. Any and all advice on where to check or what to look into is welcome.

Hi,

I am having a weird issue recently. Started about 2 weeks ago. When imaging a new computer the computer shows up in Devices twice. One device name shows as Unknown, Active, Client installed, with proper GUID and a Resource ID 167779xx. The other device name is the correct computer name, inactive, client not installed and with no GUID and a Resource ID 20971527xx. 

This seems caused client on the newly imaged computer not receiving the correct client settings. Current workaround is to manually delete these Unknown active devices in SCCM. The next time that computer checks in it register with correct information. 

Any idea what could be the cause of this issue and is there some kind log(s) I can look for clue?

Thank you,

Henry

Hello All,

I was going through the smsts.log file where i found that each package is showing like this :

MCS server:
Found location: http://J0.arun.com/SMS_DP_SMSPKG$/A0100844
Found location: https://J0.arun.com/CCMTOKENAUTH_SMS_DP_SMSPKG$/A0100844
Found location: http://J0.arun.com/NOCERT_SMS_DP_SMSPKG$/A0100844
MCS server:
Found location: http://J01.arun.com/SMS_DP_SMSPKG$/A0100844
Found location: https://J01.arun.com/CCMTOKENAUTH_SMS_DP_SMSPKG$/A0100844
Found location: http://J01.arun.com/NOCERT_SMS_DP_SMSPKG$/A0100844
MCS server:
Found location: http://J02.arun.COM/SMS_DP_SMSPKG$/A0100844
Found location: https://J02.arun.COM/CCMTOKENAUTH_SMS_DP_SMSPKG$/A0100844
Found location: http://J02.arun.COM/NOCERT_SMS_DP_SMSPKG$/A0100844

The package is same then why its showing 3 different DP servers and what it mean by MCS server ?

We recently added a new MP/DP to our second domain, to ease traffic going through the firewall. We have adjusted the boundaries accordingly, so now Boundary Group in DomainA only have DomainA servers and Boundary Group in DomainB only has the one Server.

When we try and build devices on any boundary in DomainB, after the PXE booting stage, the SMSTS.log shows:

"Using user defined MP locations: http://<DomainA_MP_DP>; <DomainA_MP_DP>"

......

"Error received 0x80072ee2 from WinHttpSendRequest"

.....

"socket 'connect' failed; 8007274c"

Can't get the log file, as it in a test Vm setup. I have a ticket logged with Microsoft, but they seem stumped. It should be using only the one server in DomainB.

Any guidance would be appreciated.

Thanks

Matthew Currie

Hi All,

I was working on one task sequence for In Place Upgrade. Win 10 1709 to Win 10 1903 is working fine. 

But Win 7 to Win 10 1903 is getting failed during Upgrade Operating System step.

I checked some of the links and added the KMS Client Keys (NPPR9-FWDCX-D2C8J-H872K-2YT43) in upgrade operating system step.

Also added one step to run vbs script.

Cscript.exe c:\windows\system32\slmgr.vbs /ipk NPPR9-FWDCX-D2C8J-H872K-2YT43

But Task Sequence is getting failed at this step.

Error: 0xC004F050 The Software Licensing Service reported that the product key is invalid

Command line Cscript.exe c:\windows\system32\slmgr.vbs /ipk NPPR9-FWDCX-D2C8J-H872K-2YT43 returned 3221549136

In my environment we are using KMS and we don't have Volumelicense. 

Any advise how to resolve this issue.

<o:p></o:p>

Hi all,

now that Windwos 10 v 1909 is out, we have started preparing our environment (SCCM Current Branch 1906) to deploy this new version and updating existing clients. 

OSD Task Sequences for new machines with 1909 seem to run pretty smooth (after figuring out some Language Pack annoyances). However, we are facing issues with SCCM Feature Update Task Sequences that bomb out after the base os installation. We are trying to update Windows 1709 and also 1809 versions. This is what we have encountered so far:

The Task Sequence for the OS upgrade starts fine, performs a few expected reboots, then displaying "Windows is working in updates 0%, 15%, ..." When it reaches 100%, this Windows Upgrade step remains at 100% for a long long time and then suddenly shows the Windows login screen. All TS Post Processing steps (i.e. Language Packs, etc.) are skipped.

SMSTS.LOG indicates, that the base OS upgrade seems to have finished without errors:

• Successfully completed the action (Upgrade Operating System) with the exit win32 code 0

After that we can discover several "Start top compile TS policy" steps, but suddenly the following errors happen:

<![LOG[Failed to initate policy evaluation for namespace 'root\ccm\policy\machine', hr=0x80041010]LOG]!><time="10:07:10.271-60" date="11-25-2019" component="TSManager" context="" type="3" thread="6284" file="utils.cpp:5007"><![LOG[Error compiling client config policies. code 80041010]LOG]!><time="10:07:10.271-60" date="11-25-2019" component="TSManager" context="" type="3" thread="6284" file="tsmanager.cpp:1577"><![LOG[Task Sequence Manager could not initialize Task Sequence Environment. code 80041010]LOG]!><time="10:07:10.271-60" date="11-25-2019" component="TSManager" context="" type="3" thread="6284" file="tsmanager.cpp:1654"><![LOG[Task sequence execution failed with error code 80041010]LOG]!><time="10:07:10.271-60" date="11-25-2019" component="TSManager" context="" type="3" thread="6284" file="tsmanager.cpp:1305">

After that the Task Sequence stops any further processing without showing any errors. Digging through all other SCCM logs I have found out that at the time time when the error above happens there is the following in CCMEXEC.LOG:

<![LOG[Detected faulty configuration. Repair will be started in 5 minutes.]LOG]!><time="10:07:11.521-60" date="11-25-2019" component="CcmExec" context="" type="3" thread="6560" file="entrypoint.cpp:3079"><![LOG[Entering main message loop.]LOG]!><time="10:07:11.521-60" date="11-25-2019" component="CcmExec" context="" type="1" thread="6560" file="entrypoint.cpp:3104"><![LOG[WM_QUIT received in the main message loop.]LOG]!><time="10:12:11.521-60" date="11-25-2019" component="CcmExec" context="" type="1" thread="6560" file="entrypoint.cpp:3121"><![LOG[Initiated repair of configuration. Service will now exit.]LOG]!><time="10:12:11.599-60" date="11-25-2019" component="CcmExec" context="" type="1" thread="6560" file="entrypoint.cpp:3130"><![LOG[Shutting down CCMEXEC...]LOG]!><time="10:12:11.599-60" date="11-25-2019" component="CcmExec" context="" type="1" thread="6560" file="shutdown.cpp:53">

This looks to me, that immediately after the OS upgrade, the system seems to start a repair of the SCCM client (for unknown reason). This repair seems to break the entire Task Sequence. 

have triple-checked countlessly that the SCCM client is healthy before the upgrade but something seems to happen during the 1909 upgrade that makes Windows trying to repair the SCCM client. 

Any thoughts what might go wrong here? 

Thanks in advance

Regards

Udo

I added manually by right click on device and

import computer information

I add my device and MAC and added it to my windows7deploy

The device is available in Devices only
I cant see the device in all systems
i cant see the device in my collection windows7deploy

I right client on my device and select add device to collection and get nothing

Can someone help me

I know that when i add a new collection i add all systems but it dont show there....

Thanks

I am using SCCM 2012, MDT 2012 and the ADK.  If I create a boot image, it does not wait for network to finish loading.  Just to make sure that wpeinit was running, I added that as a prestart command, but wpeinit.log shows that it is not configured to wait for network to load, which is really counterproductive for running a task sequence that is pulled down across the network.  Is there any way to reconfigure wpeinit so it will wait?  Or some setting I can apply in the console to the properties of the boot image that will fix this?  wpeinit.log is as follows:

2013-09-13 13:01:16.031, Info      No unattend file was found; WPEINIT is using default settings to initialize WinPE
2013-09-13 13:01:16.047, Info      ==== Initializing Display Settings ====
2013-09-13 13:01:16.047, Info      No display settings specified
2013-09-13 13:01:16.047, Info      STATUS: SUCCESS (0x00000001)
2013-09-13 13:01:16.047, Info      ==== Initializing Computer Name ====
2013-09-13 13:01:16.047, Info      Generating a random computer name
2013-09-13 13:01:16.047, Info      No computer name specified, generating a random name.
2013-09-13 13:01:16.047, Info      Renaming computer to MININT-6IF97PL.
2013-09-13 13:01:16.047, Info      Waiting on the profiling mutex handle
2013-09-13 13:01:16.047, Info      Acquired profiling mutex
2013-09-13 13:01:16.047, Info      Service winmgmt disable: 0x00000000
2013-09-13 13:01:16.047, Info      Service winmgmt stop: 0x00000000
2013-09-13 13:01:16.047, Info      Service winmgmt enable: 0x00000000
2013-09-13 13:01:16.047, Info      Released profiling mutex
2013-09-13 13:01:16.047, Info      STATUS: SUCCESS (0x00000000)
2013-09-13 13:01:16.047, Info      ==== Initializing Virtual Memory Paging File ====
2013-09-13 13:01:16.047, Info      No WinPE page file setting specified
2013-09-13 13:01:16.047, Info      STATUS: SUCCESS (0x00000001)
2013-09-13 13:01:16.047, Info      ==== Initializing Optional Components ====
2013-09-13 13:01:16.047, Info      WinPE optional component 'Microsoft-WinPE-Dot3Svc' is present
2013-09-13 13:01:16.188, Info      WinPE optional component 'Microsoft-WinPE-HTA' is present
2013-09-13 13:01:16.203, Info      WinPE optional component 'Microsoft-WinPE-MDAC' is present
2013-09-13 13:01:16.203, Info      WinPE optional component 'Microsoft-WinPE-PPPoE' is present
2013-09-13 13:01:17.109, Info      WinPE optional component 'Microsoft-WinPE-WMI' is present
2013-09-13 13:01:17.125, Info      WinPE optional component 'Microsoft-WinPE-WSH' is present
2013-09-13 13:01:17.141, Info      STATUS: SUCCESS (0x00000000)
2013-09-13 13:01:17.141, Info      ==== Initializing Network Access and Applying Configuration ====
2013-09-13 13:01:17.141, Info      No EnableNetwork unattend setting was specified; the default action for this context is to enable networking support.
2013-09-13 13:01:17.141, Info      Global handle for profiling mutex is non-null
2013-09-13 13:01:17.141, Info      Waiting on the profiling mutex handle
2013-09-13 13:01:17.141, Info      Acquired profiling mutex
2013-09-13 13:01:17.391, Info      Install MS_MSCLIENT: 0x00000000
2013-09-13 13:01:17.391, Info      Install MS_NETBIOS: 0x00000000
2013-09-13 13:01:17.438, Info      Install MS_SMB: 0x00000000
2013-09-13 13:01:17.516, Info      Install MS_TCPIP6: 0x00000000
2013-09-13 13:01:17.922, Info      Install MS_TCPIP: 0x00000000
2013-09-13 13:01:17.922, Info      Service dhcp start: 0x00000000
2013-09-13 13:01:17.922, Info      Service lmhosts start: 0x00000000
2013-09-13 13:01:17.969, Info      Service ikeext start: 0x00000000
2013-09-13 13:01:18.063, Info      Service mpssvc start: 0x00000000
2013-09-13 13:01:18.063, Info      Released profiling mutex
2013-09-13 13:01:18.063, Info      Spent 922ms installing network components
2013-09-13 13:01:18.313, Info      Installing device ms_ndiswanip X:\windows\INF\netrasa.inf succeeded
2013-09-13 13:01:18.469, Info      Installing device root\kdnic X:\windows\INF\kdnic.inf succeeded
2013-09-13 13:01:18.594, Info      Installing device ms_ndiswanipv6 X:\windows\INF\netrasa.inf succeeded
2013-09-13 13:01:25.955, Info      Installing device pci\ven_8086&dev_153a X:\windows\INF\oem1.inf succeeded
2013-09-13 13:01:26.174, Info      Installing device ms_ndiswanbh X:\windows\INF\netrasa.inf succeeded
2013-09-13 13:01:26.174, Info      Spent 8109ms installing network drivers
2013-09-13 13:01:26.205, Info      WaitForNetworkToInitializeIgnoringErrors: Configured to not wait for Network.
2013-09-13 13:01:26.205, Info      STATUS: SUCCESS (0x003d0001)
2013-09-13 13:01:26.205, Info      ==== Applying Firewall Settings ====
2013-09-13 13:01:26.205, Info      STATUS: SUCCESS (0x00000001)
2013-09-13 13:01:26.205, Info      ==== Executing Synchronous User-Provided Commands ====
2013-09-13 13:01:26.205, Info      STATUS: SUCCESS (0x00000001)
2013-09-13 13:01:26.205, Info      ==== Executing Asynchronous User-Provided Commands ====
2013-09-13 13:01:26.205, Info      STATUS: SUCCESS (0x00000001)
2013-09-13 13:01:26.205, Info      ==== Applying Shutdown Settings ====
2013-09-13 13:01:26.205, Info      No shutdown setting was specified
2013-09-13 13:01:26.205, Info      STATUS: SUCCESS (0x00000001)
2013-09-13 13:01:49.899, Info      No unattend file was found; WPEINIT is using default settings to initialize WinPE
2013-09-13 13:01:49.899, Info      ==== Initializing Display Settings ====
2013-09-13 13:01:49.899, Info      No display settings specified
2013-09-13 13:01:49.899, Info      STATUS: SUCCESS (0x00000001)
2013-09-13 13:01:49.899, Info      ==== Initializing Computer Name ====
2013-09-13 13:01:49.899, Info      Generating a random computer name
2013-09-13 13:01:49.899, Info      Computer is already named and no new name is specified, returning success.
2013-09-13 13:01:49.899, Info      STATUS: SUCCESS (0x00000001)
2013-09-13 13:01:49.899, Info      ==== Initializing Virtual Memory Paging File ====
2013-09-13 13:01:49.899, Info      No WinPE page file setting specified
2013-09-13 13:01:49.899, Info      STATUS: SUCCESS (0x00000001)
2013-09-13 13:01:49.899, Info      ==== Initializing Optional Components ====
2013-09-13 13:01:49.899, Info      WinPE optional component 'Microsoft-WinPE-Dot3Svc' is present
2013-09-13 13:01:49.946, Info      WinPE optional component 'Microsoft-WinPE-HTA' is present
2013-09-13 13:01:49.961, Info      WinPE optional component 'Microsoft-WinPE-MDAC' is present
2013-09-13 13:01:49.961, Info      WinPE optional component 'Microsoft-WinPE-PPPoE' is present
2013-09-13 13:01:50.024, Info      WinPE optional component 'Microsoft-WinPE-WMI' is present
2013-09-13 13:01:50.024, Info      WinPE optional component 'Microsoft-WinPE-WSH' is present
2013-09-13 13:01:50.024, Info      STATUS: SUCCESS (0x00000000)
2013-09-13 13:01:50.024, Info      ==== Initializing Network Access and Applying Configuration ====
2013-09-13 13:01:50.024, Info      No EnableNetwork unattend setting was specified; the default action for this context is to enable networking support.
2013-09-13 13:01:50.024, Info      Waiting on the profiling mutex handle
2013-09-13 13:01:50.024, Info      Acquired profiling mutex
2013-09-13 13:01:50.039, Info      Install MS_MSCLIENT: 0x00000000
2013-09-13 13:01:50.039, Info      Install MS_NETBIOS: 0x00000000
2013-09-13 13:01:50.039, Info      Install MS_SMB: 0x00000000
2013-09-13 13:01:50.039, Info      Install MS_TCPIP6: 0x00000000
2013-09-13 13:01:50.039, Info      Install MS_TCPIP: 0x00000000
2013-09-13 13:01:50.039, Info      Service dhcp start: 0x00000000
2013-09-13 13:01:50.039, Info      Service lmhosts start: 0x00000000
2013-09-13 13:01:50.039, Info      Service ikeext start: 0x00000000
2013-09-13 13:01:50.039, Info      Service mpssvc start: 0x00000000
2013-09-13 13:01:50.039, Info      Released profiling mutex
2013-09-13 13:01:50.039, Info      Spent 15ms installing network components
2013-09-13 13:01:50.258, Info      Installing device ms_ndiswanip X:\windows\INF\netrasa.inf succeeded
2013-09-13 13:01:50.415, Info      Installing device ms_ndiswanipv6 X:\windows\INF\netrasa.inf succeeded
2013-09-13 13:01:50.712, Info      Installing device ms_ndiswanbh X:\windows\INF\netrasa.inf succeeded
2013-09-13 13:01:50.712, Info      Spent 672ms installing network drivers
2013-09-13 13:01:50.728, Info      WaitForNetworkToInitializeIgnoringErrors: Configured to not wait for Network.
2013-09-13 13:01:50.728, Info      STATUS: SUCCESS (0x003d0001)
2013-09-13 13:01:50.728, Info      ==== Applying Firewall Settings ====
2013-09-13 13:01:50.728, Info      STATUS: SUCCESS (0x00000001)
2013-09-13 13:01:50.728, Info      ==== Executing Synchronous User-Provided Commands ====
2013-09-13 13:01:50.728, Info      STATUS: SUCCESS (0x00000001)
2013-09-13 13:01:50.728, Info      ==== Executing Asynchronous User-Provided Commands ====
2013-09-13 13:01:50.728, Info      STATUS: SUCCESS (0x00000001)
2013-09-13 13:01:50.728, Info      ==== Applying Shutdown Settings ====
2013-09-13 13:01:50.728, Info      No shutdown setting was specified
2013-09-13 13:01:50.728, Info      STATUS: SUCCESS (0x00000001)

We have MDT configured to upgrade windows 7 computers to Windows 10 on a network and it works great with windows 10 Build 1903. When the 1909 Build came out I added it to the MDT server in the same way I added the 1903 build. Same settings, same method, same scripts but with a different task sequence ID and of course the new imported operating system files. I have had nothing but issues with the upgrade. Most times it errors out when starting the operating system install with the error " an unknown command line option was specified /auto"

When I have gotten it to upgrade, the computer reboots after the install operating system install step and hangs the computer, just a complete blank screen. you have to hard shut off the computer then it starts back up with doing updates and continues to complete the installation.

Either scenario is unacceptable and I was wondering if anyone else has seen an issue with the new build.

Hi Team,

we are deploying Operating system through software center and we have capture the windows setting ( Time zone and Org name ) in the Task sequence. we looking for the option to restore the captured time zone in the TS.  

Install Operating system -> Apply windows settings. 

I believe we canamend those setting inunattended file. Can you please guide how to apply the settings ?

Regards,

Senthil