Hello Experts,

I need your expertise suggestion on the below scenario –

One of our customer has SCCM 2012 R2 SP1 CU2 infrastructure and they will take time to upgrade to 1610. Till the time they were using Windows 10 1507 (build 10240) but it will be EOL by March 2017.

https://blogs.technet.microsoft.com/windowsitpro/2017/01/19/windows-10-v1607-media-now-available/

The below link says that deployment and servicing of Windows 10 1511 (build 10586) is supported with SCCM 2012 R2 SP1 CU2 infrastructure though -

https://blogs.technet.microsoft.com/enterprisemobility/2015/10/27/system-center-configuration-manager-support-for-windows-10-and-microsoft-intune/

Windows 10 1511 (build 10586) will be EOL by November 2017.

https://www.niallbrady.com/2016/08/12/when-do-different-versions-of-windows-10-become-unsupported/

My question is –

1. Will be it a good idea to work with Windows 10 1511 to crate OS images and deploy with SCCM 2012 Task Sequence for that customer?
2. Is it  Microsoft supported scenario to upgrade existing machines from Windows 10 1507 to windows 10 1511 using SCCM 2012 Task Sequence?

Any other inputs along with answers for the above questions will be highly appreciated.

Thank you.

Hi guys, 

We have been having a few issues lately with PXE booting and a lot of policy errors when we do an OSD deployment, after a little digging i checked the MP_Policy.log of my MP and found the following in a constant loop.

I have tried reinstalling the MP, removing any policies i have and adding them again with no luck at all.

any assistance would be appreciated.

Thanks Leon

Hello. So I will start out with saying that I have been able to successfully image a computer with this task sequence when the computer is in legacy BIOS, but when I change it to UEFI w/ secure boot enabled (or even with it disabled so far) it does not work. It boots into PXE fine, then our Task Sequence Wizard starts, allows me to go through all of our UDI wizard options until it begins. Then it starts the TS where it formats and partitions the disk. It displays no errors and simply reboots within about 2 minutes of starting the process. 

When I look at the smsts.log file I see:

Failed to read filesystem from OSDPartitions2FileSystem, not formattingOSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)

Which is preceeded by:

Reading partition size info for partition 1 OSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
Remaining size before partition: 127720135680 OSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
size units: SIZE_MBOSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
Set partition size: 536870912OSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
Remaining size after partition 1: 127183264768 OSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
Reading partition size info for partition 2 OSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
Remaining size before partition: 127183264768 OSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
size units: SIZE_MBOSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
Set partition size: 134217728OSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
Remaining size after partition 2: 127049047040 OSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)

and suceeded by:

Reading partition size info for partition 3 OSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
Remaining size before partition: 127049047040 OSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
size units: SIZE_PERCENTOSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
100% size specified.OSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
Remaining size after partition 3: 0OSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
Checking volume 'C:' for BitLockerOSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
Volume 'C:' is on disk '0l'OSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
Volume 'C:' is fully decryptedOSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
Checking volume 'X:' for BitLockerOSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
diskpart: list volume 
select disk 0
clean
convert gpt
create partition PRIMARY size=300
format quick fs=ntfs label="Windows RE Tools"
attributes volume set nodefaultdriveletter noerr
OSDDiskPart 6/23/2016 10:05:30 AM1136 (0x0470)
Found an EFI partition to configure.OSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
S partition is not used, will use it.OSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
diskpart: list volume 
select disk 0
clean
convert gpt
create partition PRIMARY size=300
format quick fs=ntfs label="Windows RE Tools"
attributes volume set nodefaultdriveletter noerr
create partition EFI size=512
assign letter=S
format fs=fat32 quick
OSDDiskPart 6/23/2016 10:05:30 AM1136 (0x0470)
diskpart: list volume 
select disk 0
clean
convert gpt
create partition PRIMARY size=300
format quick fs=ntfs label="Windows RE Tools"
attributes volume set nodefaultdriveletter noerr
create partition EFI size=512
assign letter=S
format fs=fat32 quick
create partition MSR size=128
OSDDiskPart 6/23/2016 10:05:30 AM1136 (0x0470)
diskpart: list volume 
select disk 0
clean
convert gpt
create partition PRIMARY size=300
format quick fs=ntfs label="Windows RE Tools"
attributes volume set nodefaultdriveletter noerr
create partition EFI size=512
assign letter=S
format fs=fat32 quick
create partition MSR size=128
create partition PRIMARY
assign
OSDDiskPart 6/23/2016 10:05:30 AM1136 (0x0470)
Diskpart: list volume 
select disk 0
clean
convert gpt
create partition PRIMARY size=300
format quick fs=ntfs label="Windows RE Tools"
attributes volume set nodefaultdriveletter noerr
create partition EFI size=512
assign letter=S
format fs=fat32 quick
create partition MSR size=128
create partition PRIMARY
assign
rescan
 list volume
OSDDiskPart 6/23/2016 10:05:30 AM1136 (0x0470)
Executing diskpart script: list volume 
select disk 0
clean
convert gpt
create partition PRIMARY size=300
format quick fs=ntfs label="Windows RE Tools"
attributes volume set nodefaultdriveletter noerr
create partition EFI size=512
assign letter=S
format fs=fat32 quick
create partition MSR size=128
create partition PRIMARY
assign
rescan
 list volume
OSDDiskPart 6/23/2016 10:05:30 AM1136 (0x0470)
Command line for extension .exe is "%1" %*OSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
Set command line: "X:\WINDOWS\system32\diskpart.exe" /s "X:\WINDOWS\TEMP\DiskPartScript.txt"OSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
Executing command line: "X:\WINDOWS\system32\diskpart.exe" /s "X:\WINDOWS\TEMP\DiskPartScript.txt"OSDDiskPart6/23/2016 10:05:30 AM1136 (0x0470)
Process completed with exit code 0OSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Formatting partitionsOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Partition: 1 PRIMARYOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Partition: 2 EFIOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Found EFI partition: 2OSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
EFI file system: FAT32OSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Partition: 3 MSROSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Found MSR partition: 3OSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Partition: 4 PRIMARYOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Adding logical drive: C:OSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Adding logical drive: S:OSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Skipping non-local logical drive: X:OSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Formatting drive C: with NTFS filesystem, method quickOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Creating instance of service loaderOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Loading serviceOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Waiting for service to initializeOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Querying for software providersOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Found a VDS software providerOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Querying for IVdsSwProviderOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Querying for packsOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Found a VDS packOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Querying for IVdsPackOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Querying for volumesOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Found a VDS software providerOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Querying for IVdsSwProviderOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Querying for packsOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Found a VDS packOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Querying for IVdsPackOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Querying for volumesOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Found a VDS volumeOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Querying for IVdsVolumeMFOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Querying for access pathsOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Found a VDS volumeOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Querying for IVdsVolumeMFOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Querying for access pathsOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Found a volume with access path 'C:\'OSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Querying for IVdsVolumeOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Querying for IVdsVolumeMFOSDDiskPart6/23/2016 10:05:33 AM1136 (0x0470)
Executing command line: X:\WINDOWS\system32\cmd.exe /kTSBootShell6/23/2016 10:05:33 AM976 (0x03D0)
The command completed successfully.TSBootShell6/23/2016 10:05:33 AM976 (0x03D0)
Successfully launched command shell.TSBootShell6/23/2016 10:05:33 AM976 (0x03D0)
OSDDiskPart.exe completed successfullyOSDDiskPart6/23/2016 10:05:39 AM1136 (0x0470)
Process completed with exit code 0TSManager6/23/2016 10:05:39 AM1456 (0x05B0)
!--------------------------------------------------------------------------------------------!TSManager6/23/2016 10:05:39 AM1456 (0x05B0)
Successfully completed the action (Format and Partition Disk (UEFI)) with the exit win32 code 0TSManager6/23/2016 10:05:39 AM1456 (0x05B0)
MP server http://USTLVUOI519.O-I.INTRATEST. Ports 80,443. CRL=false.TSManager6/23/2016 10:05:39 AM1456 (0x05B0)
Setting authenticatorTSManager6/23/2016 10:05:39 AM1456 (0x05B0)
Set authenticator in transportTSManager6/23/2016 10:05:39 AM1456 (0x05B0)
Sending StatusMessageTSManager6/23/2016 10:05:39 AM1456 (0x05B0)
Setting message signatures.TSManager6/23/2016 10:05:39 AM1456 (0x05B0)
Setting the authenticator.TSManager6/23/2016 10:05:39 AM1456 (0x05B0)
CLibSMSMessageWinHttpTransport::Send: URL: USTLVUOI519.O-I.INTRATEST:80  CCM_POST /ccm_system/requestTSManager6/23/2016 10:05:39 AM1456 (0x05B0)
Request was successful.TSManager6/23/2016 10:05:39 AM1456 (0x05B0)
Set a global environment variable _SMSTSLastActionRetCode=0TSManager6/23/2016 10:05:39 AM1456 (0x05B0)
Set a global environment variable _SMSTSLastActionSucceeded=trueTSManager6/23/2016 10:05:39 AM1456 (0x05B0)
Expand a string: %_SMSTSMDataPath%\LogsTSManager6/23/2016 10:05:39 AM1456 (0x05B0)

Then the log just abruptly ends, without an error. I am assuming that is when it reboots and then goes through it's normal boot cycle and when it gets to the HDD it states that an OS could not be found.

Little bit more information: We use SCCM 2012 R2 SP1 version 5.0.8239.1203 (with Windows 10 ADK installed) with MDT 2013 Update 2 I believe. And not that it matters too much to this process but in our test environment (where I am attempting this image) we also have Adaptiva version 5.5.659.3 which is an alternate content provider for SCCM instead of using a distribution point at each site we have what is called Adaptiva OneSite which allows us to have 1 DP in our global organization.

Let me know if more information is needed, any little bit helps. Thanks.

Having issues finding an updated version of the "Surface Firmware Tool" for the Surface Pro 4.

Does one exist yet ?

Any assistance would be appreciated. 

I am trying to import Windows 10 drivers in my current SCCM 2012 R2 which is running on Windows Server 2012 R2.

But I am getting the error :  The selected driver is not applicable to any supported platforms

How do I resolve this.? Can someone please help. Thanks in advance.

Aakash Saxena

Hello All,

I am currently experiencing trouble with Lenovo ThinkStation P300 and P310 systems, containing a 1TB HDD and a DVD-drive. The customer is still using SCCM 2012 R2 SP1 CU 1 (1203). The task sequence is a standard TS that installs a previously captured wim, containing most updates and using the PreserveDriveLetter variable set to "false". The format step is set to BIOS and one single large partition. The OS is targeted to a driveletter stored in a variable, so the parition is given the variable "OSDisk". Windows is successfully installed to C: at this point.

When installing Windows 7 Enterprise on the systems, when the client install comes up, it tries to install itself on the DVD-drive, which is D: at this point (verified by starting diskpart and checking volumes).

The client.msi.log clearly shows this:

MSI (s) (28:2C) [10:41:26:131]: Note: 1: 2304 2: 21 3: D:\
MSI (s) (28:2C) [10:41:26:131]: PROPERTY CHANGE: Modifying PrimaryVolumeSpaceAvailable property. Its current value is '0'. Its new value: '1876583224'.
MSI (s) (28:2C) [10:41:26:131]: PROPERTY CHANGE: Modifying PrimaryVolumeSpaceRequired property. Its current value is '0'. Its new value: '528'.
MSI (s) (28:2C) [10:41:26:131]: PROPERTY CHANGE: Modifying PrimaryVolumeSpaceRemaining property. Its current value is '0'. Its new value: '1876582696'.
MSI (s) (28:2C) [10:41:26:131]: PROPERTY CHANGE: Adding PrimaryVolumePath property. Its value is 'C:'.
MSI (s) (28:2C) [10:41:26:131]: PROPERTY CHANGE: Modifying OutOfDiskSpace property. Its current value is '0'. Its new value: '1'.
MSI (s) (28:2C) [10:41:26:131]: PROPERTY CHANGE: Modifying OutOfNoRbDiskSpace property. Its current value is '0'. Its new value: '1'.
MSI (s) (28:2C) [10:41:26:131]: Note: 1: 2205 2:  3: FilesInUse
MSI (s) (28:2C) [10:41:26:131]: Note: 1: 2304 2: 21 3: D:\
MSI (s) (28:2C) [10:41:26:131]: Note: 1: 2304 2: 21 3: D:\
MSI (s) (28:2C) [10:41:26:131]: Note: 1: 1601 2: D: 3: 2.502 4: 0
MSI (s) (28:2C) [10:41:26:131]: Product: Configuration Manager Client -- Disk full: Out of disk space -- Volume: 'D:'; required space: 2.502 KB; available space: 0 KB.  Free some disk space and retry.
Disk full: Out of disk space -- Volume: 'D:'; required space: 2.502 KB; available space: 0 KB.  Free some disk space and retry.
MSI (s) (28:2C) [10:41:26:131]: Transforming table InstallExecuteSequence.
Action ended 10:41:26: InstallValidate. Return value 3.

The same tasksequence works on all other systems we have here - be it Lenovo Laptops, Dell Laptops and Desktops or VMware VMs.

Does anyone have an idea what I can do to get the client to install "normally"? I've never had this problem anywhere and google doesn't offer much help in this case :-/

BR,

Fred

<![LOG[In policy:ScopeId_8D416609_5606_4337_B899_0881BFB0E717_DeploymentType_7a968b20_3459_46a5_ad2f_ea625ea7afd7_2_Discovery_PolicyDocument, rule:5fed7d11_23e5_46ef_9648_ec05eb82e271__ScopeId_8D416609_5606_4337_B899_0881BFB0E717_DeploymentType_7a968b20_3459_46a5_ad2f_ea625ea7afd7_2_Discovery_PolicyDocument status is:Conformant]LOG]!><time="14:05:09.751-120" date="01-23-2017" component="DCMReporting" context="" type="1" thread="7824" file="dcmreporting.cpp:698">
<![LOG[CDCMReporting::ProcessSynchronizationDetailReport]LOG]!><time="14:05:09.751-120" date="01-23-2017" component="DCMReporting" context="" type="1" thread="7824" file="dcmreporting.cpp:822">
<![LOG[CDCMReporting::BuildReport failed (0x87d00215).]LOG]!><time="14:05:09.753-120" date="01-23-2017" component="DCMReporting" context="" type="3" thread="7824" file="dcmreporting.cpp:208">
<![LOG[CDCMReporting::FinalRelease]LOG]!><time="14:05:09.753-120" date="01-23-2017" component="DCMReporting" context="" type="1" thread="7824" file="dcmreporting.cpp:2282">

i can't install software from sccm to client because the error

i have latest sccm version 1610

client is Windows 7 x86 computer

Hi, 

We have install SCCM Build 1610 and deploy the Pre-Production Client to a validation collection. (5.00.8458.1007)

In the same time we have modify the master task sequence Windows 10, and check : "Use Pre-production client package when available" in the step Configure Windows and Configuration Manager.

On the box Pre-Production Client Package we have browse to the Pre-Production Package : "Microsoft Corporation Configuration Manager Client Piloting Package"

At the end of the task sequence we don't have the Pre-Production Client (5.00.8458.1007) on the computer but the production client (Old client 5.008412.1007)

How can we use this functionnality in the task sequence for validated the pre-production client in the Windows 10 Master Task Sequence. 

Thanks for your help 

Hi,

We're trying to services our OS images (.wims) through SCCM. However when we right-click the OS Image and choose for 'Schedule Updates' we don't see all the updates. The image targeted is a freshly captured Windows 10 enterprise 1607. The updates I can see:



However, we do import ALL the updates in SCCM for Windows 10 (shown below).

Server: Windows Server 2012 R2

SCCM: 1610

Windows ADK: 10.1.10586.0 (It's this version because there's a bug in the last version according to our SCCM-expert (netSH codes?))

Is this also a bug, or is there something else going on?

Thanks in advance,

Sander.

Hi all,

Hope someone can help.

Since last week our SCCM isn’t completing build task sequences.  They seem to be failing during software installation and sometimes before that at the driver package or updates stage.

Windows 7 machines generally fail at the software installation stage again at random points. I have noticed that we have a black background instead of our normal background when building.

Windows 10 seems to be failing after drivers and doesn’t install any additional software. All machines are on the domain with the correct operating system

The windows 7 machines have a folder on the C drive called _smstasksequence which normally indicates the task sequence didn’t complete successfully as this folder is normally deleted after completion. There are four log files in the folder which looking at with CMTrace show numerous errors.

The only thing that has changed in the last week is we had two new model laptops (HP Probook 430 and a HP Probook 650 G2) which we created a new driver package for. (Wondering if any of these drivers have overwritten other drivers such as the Intel network card driver)

Previous task sequences which we never change have also produced the same error and issues as above

Log file below is for the HP 650 G1

<![LOG[DAV response string is:
<![CDATA[<?xml version="1.0" encoding="utf-8" ?><D:multistatus xmlns:D="DAV:"><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/sccm?/357EA35E-F070-4ABD-B46C-217CD752E2B4/</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:supportedlock/><D:getetag/><D:creationdate/><D:iscollection>1</D:iscollection><D:resourcetype><D:collection/></D:resourcetype><D:ishidden>0</D:ishidden><D:displayname>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/sccm?/357EA35E-F070-4ABD-B46C-217CD752E2B4/</D:displayname><D:getlastmodified></D:getlastmodified><D:getcontentlanguage/><D:getcontentlength>0</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/2011_BEATS_SPEAKER_M.INI</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/2011_BEATS_SPEAKER_M.INI</D:displayname><D:getlastmodified>Fri, 25 Oct 2013 02:13:02 GMT</D:getlastmodified><D:getcontentlength>32578</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/2011_SRS_SPEAKER_L.INI</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/2011_SRS_SPEAKER_L.INI</D:displayname><D:getlastmodified>Fri, 25 Oct 2013 02:13:02 GMT</D:getlastmodified><D:getcontentlength>32578</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/2hps.ico</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/2hps.ico</D:displayname><D:getlastmodified>Tue, 18 Dec 2007 17:40:28 GMT</D:getlastmodified><D:getcontentlength>3774</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/AESTAC64.dll</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/AESTAC64.dll</D:displayname><D:getlastmodified>Tue, 15 Oct 2013 01:50:48 GMT</D:getlastmodified><D:getcontentlength>207048</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/AESTACap.dll</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/AESTACap.dll</D:displayname><D:getlastmodified>Tue, 15 Oct 2013 01:50:48 GMT</D:getlastmodified><D:getcontentlength>180936</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/AESTAR64.dll</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/AESTAR64.dll</D:displayname><D:getlastmodified>Thu, 29 Mar 2012 10:48:38 GMT</D:getlastmodified><D:getcontentlength>74336</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/AESTARen.dll</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/AESTARen.dll</D:displayname><D:getlastmodified>Thu, 29 Mar 2012 10:47:14 GMT</D:getlastmodified><D:getcontentlength>68192</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/AESTCo64.dll</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/AESTCo64.dll</D:displayname><D:getlastmodified>Mon, 02 Mar 2009 12:47:04 GMT</D:getlastmodified><D:getcontentlength>90624</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/AESTCom.dll</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/AESTCom.dll</D:displayname><D:getlastmodified>Mon, 02 Mar 2009 12:47:06 GMT</D:getlastmodified><D:getcontentlength>86016</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/AESTEC64.dll</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/AESTEC64.dll</D:displayname><D:getlastmodified>Fri, 09 Oct 2009 12:45:38 GMT</D:getlastmodified><D:getcontentlength>442368</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/AESTECap.dll</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4/sccm?/AESTECap.dll</D:displayname><D:getlastmodified>Fri, 09 Oct 2009 12:45:54 GMT</D:getlastmodified><D:getcontentlength>380928</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/357EA35E-F070-4ABD-B46C-217CD752E2B4  01/01/1601 00:00:00 22772648 (0x15B7BA8)
<![LOG[DAV response string is:
<![CDATA[<?xml version="1.0" encoding="utf-8" ?><D:multistatus xmlns:D="DAV:"><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/sccm?/767DD607-F349-4895-B366-E7284CB70CE4/</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:supportedlock/><D:getetag/><D:creationdate/><D:iscollection>1</D:iscollection><D:resourcetype><D:collection/></D:resourcetype><D:ishidden>0</D:ishidden><D:displayname>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/sccm?/767DD607-F349-4895-B366-E7284CB70CE4/</D:displayname><D:getlastmodified></D:getlastmodified><D:getcontentlanguage/><D:getcontentlength>0</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/767DD607-F349-4895-B366-E7284CB70CE4/sccm?/3f3ca95b-3978-4168-b47b-5444f42d6c89.devicemetadata-ms</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/767DD607-F349-4895-B366-E7284CB70CE4/sccm?/3f3ca95b-3978-4168-b47b-5444f42d6c89.devicemetadata-ms</D:displayname><D:getlastmodified>Tue, 17 Sep 2013 03:19:22 GMT</D:getlastmodified><D:getcontentlength>938</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/767DD607-F349-4895-B366-E7284CB70CE4/sccm?/46a6fdbe-c823-4579-bab6-35f67e01f793.devicemetadata-ms</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/767DD607-F349-4895-B366-E7284CB70CE4/sccm?/46a6fdbe-c823-4579-bab6-35f67e01f793.devicemetadata-ms</D:displayname><D:getlastmodified>Tue, 17 Sep 2013 03:19:22 GMT</D:getlastmodified><D:getcontentlength>833</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/767DD607-F349-4895-B366-E7284CB70CE4/sccm?/heci.cat</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/767DD607-F349-4895-B366-E7284CB70CE4/sccm?/heci.cat</D:displayname><D:getlastmodified>Tue, 17 Sep 2013 03:19:22 GMT</D:getlastmodified><D:getcontentlength>12079</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/767DD607-F349-4895-B366-E7284CB70CE4/sccm?/heci.inf</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/767DD607-F349-4895-B366-E7284CB70CE4/sccm?/heci.inf</D:displayname><D:getlastmodified>Tue, 17 Sep 2013 03:19:22 GMT</D:getlastmodified><D:getcontentlength>11167</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/767DD607-F349-4895-B366-E7284CB70CE4/sccm?/x64</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:supportedlock/><D:getetag/><D:creationdate/><D:iscollection>1</D:iscollection><D:resourcetype><D:collection/></D:resourcetype><D:ishidden>0</D:ishidden><D:displayname>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/767DD607-F349-4895-B366-E7284CB70CE4/sccm?/x64</D:displayname><D:getlastmodified>Tue, 17 Sep 2013 03:19:22 GMT</D:getlastmodified><D:getcontentlanguage/><D:getcontentlength>0</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/767DD607-F349-4895-B366-E7284CB70CE4/sccm?/x64/HECIx64.sys</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>/HECIx64.sys</D:displayname><D:getlastmodified>Tue, 17 Sep 2013 03:19:22 GMT</D:getlastmodified><D:getcontentlength>64472</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/767DD607-F349-4895-B366-E7284CB70CE4/sccm?/x64/TEEDriverx64.sys</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>/TEEDriverx64.sys</D:displayname><D:getlastmodified>Tue, 17 Sep 2013 03:19:22 GMT</D:getlastmodified><D:getcontentlength>99288</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/767DD607-F349-4895-B366-E7284CB70CE4/sccm?/x64/WdfCoInstaller01011.dll</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>/WdfCoInstaller01011.dll</D:displayname><D:getlastmodified>Tue, 17 Sep 2013 03:19:22 GMT</D:getlastmodified><D:getcontentlength>1795952</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/767DD607-F349-4895-B366-E7284CB70CE4/sccm?/x86</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:supportedlock/><D:getetag/><D:creationdate/><D:iscollection>1</D:iscollection><D:resourcetype><D:collection/></D:resourcetype><D:ishidden>0</D:ishidden><D:displayname>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/767DD607-F349-4895-B366-E7284CB70CE4/sccm?/x86</D:displayname><D:getlastmodified>Tue, 17 Sep 2013 03:19:22 GMT</D:getlastmodified><D:getcontentlanguage/><D:getcontentlength>0</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/767DD607-F349-4895-B366-E7284CB70CE4/sccm?/x86/HECI.sys</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>/HECI.sys</D:displayname><D:getlastmodified>Tue, 17 Sep 2013 03:19:22 GMT</D:getlastmodified><D:getcontentlength>56280</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/767DD607-F349-4895-B366-E7284CB70CE4/sccm?/x86/TEEDriver.sys</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayname>/TEEDriver.sys</D:displayname><D:getlastmodified>Tue, 17 Sep 2013 03:19:22 GMT</D:getlastmodified><D:getcontentlength>85464</D:getcontentlength></D:prop></D:propstat></D:response><D:response><D:href>http://MCC-SCCM1.monmouthshire.gov.uk/SMS_DP_SMSPKG$/767DD607-F349-4895-B366-E7284CB70CE4/sccm?/x86/WdfCoInstaller01011.dll</D:href><D:propstat><D:status>HTTP/1.1 200 OK</D:status><D:prop><D:getcontenttype/><D:lockdiscovery/><D:supportedlock/><D:getetag/><D:getcontentlanguage/><D:iscollection>0</D:iscollection><D:creationdate/><D:resourcetype/><D:ishidden>0</D:ishidden><D:displayn

I am trying to add a "local" user account to the Administrator group using Windows System Image Manager. I have added the amd64_Microsoft-Windows-Shell-Setup_neutral to my "7 oobe System" pass. Under UserAccounts I have added the local account;

Description: Local User Administrator

DisplayName: Admin

Group: Administrators

Name: Admin

I have set the password. The answer file completes and modifies all info except for this account..

Am I missing something?

DHeinz

-- Adam

Hi, would it work if i used the method described on this site below in sccm integrated with mdt and just replaced the task sequence id variable with _SMSTSPackageID and the package id of the task sequence?

https://the-d-spot.org/2012/07/20/how-to-use-different-settings-per-task-sequence-with-mdt-2012/

question 2: If i remove panes from the xml file, and put what would be typed into them in the customsettings.ini file such as OSDomainname, would it be the same as using the skip variable in mdt?

When using PKI certificates, Microsoft recommends using the Auto-enrollment method to enroll the client authentication certificate yet they also state Group Policy is disabled while the Task Sequence is running so obviously the system will not enroll the cert the first time the computer reboots after joining the domain or any other restart steps since that occurs during the TS while GP processing is disabled. That also means the cert will still not be enrolled when the client is installed during the "Setup Windows and ConfigMgr" step therefore the client doesn't really become fully operational until the Task Sequence actually completes and Group Policy processing is enabled which will occur within 90 minutes (GP refresh) after the TS completes. Can someone confirm this is true that auto cert enrollment will not occur until after the TS completes?

Hi All,

I have been running runbooks from MDT 2012 successfully. But Im know trying to use this in SCCM 2012 with MDT intregration.

But, its not OSD task sequence, its a cuom tast with just one task "Execute run book". Im able to run this from runbook console passing OSDComputername manually.

The runbook adds the computer to an security group.

SMSTS.log

Failed to run the action: Add "GP Deny WSUS and FCS". Execution has been aborted 23/08/2013 17:25:50 24312 (0x5EF8)
Set authenticator in transport 23/08/2013 17:25:50 24312 (0x5EF8)
Failed to run the last action: Add "GP Deny WSUS and FCS". Execution of task sequence failed.
Incorrect function. (Error: 00000001; Source: Windows) 23/08/2013 17:25:50 24312 (0x5EF8)
Set authenticator in transport 23/08/2013 17:25:50 24312 (0x5EF8)
Task Sequence Engine failed! Code: enExecutionFail 23/08/2013 17:26:12 24312 (0x5EF8)
**************************************************************************** 23/08/2013 17:26:12 24312 (0x5EF8)
Task sequence execution failed with error code 80004005 23/08/2013 17:26:12 24312 (0x5EF8)
Cleaning Up. 23/08/2013 17:26:12 24312 (0x5EF8)
Removing Authenticator 23/08/2013 17:26:12 24312 (0x5EF8)
Cleaning up task sequence folder 23/08/2013 17:26:12 24312 (0x5EF8)
File "E:\_SMSTaskSequence\TSEnv.dat" does not exist. (Code 0x80070002) 23/08/2013 17:26:12 24312 (0x5EF8)

Can you execute a runbbok without setting the enviroment an MDT OSD TS creates?

Can you run more than one action under SMSTSPostAction? How?

If not, can you set the Task Sequence Variable twice in an action? So for the first one you want to remove a network drive and the second one would reboot.

Hello Everyone,

I got a problem with the Network Access Account on SCCM 2012. I didn't have any problem previously and can deploy OS successfully. The problem started last week when I tried to deploy an OS. It gave me a error on Task Sequence then I searched for the error and found that its related with the Network Access Account. On SCCM Config Manager I checked the Network Access Account and found that I had the wrong password. But the bigger problem starts here: on configManager Administration/Security/accounts window I open my NAS properties and on the verify window tried to reach a simple network share and it says the password is wrong, then I change the password and tried to verify one more time and it successfully reaches the share, I simply click apply and OK as usual but when I open the properties window I always see the old password stays there. I tried to change the password maybe 100 time but I didn't work. My NAS is a normal domain account with Domain Users permissions, I ve already checked the password, account and password never expires options, they are all rightly configured. I also tried to make a new account to use as a NAS, then I set it on SCCM as a NAS but the result is always the same. Accounts have wrong password and I cant change and save it. Actually I can change till I close the properties window then its all gone , reset to old wrong password. Please help me with that, I am googling it like 2 days and found that the same thing happened to 2 other people, but there is no solution... 

Dear all,

I created a TS for application updates in the environment (SCCM 1802), deployed it required with an end date. So, the end date is reached but on some clients the TS do not run immediately. Via Client Center is it possible to see the advertisement but the user cannot see the TS in software center and didn't run immediately after the client is online. But if I rerun the advertisement via Client Center or Collection Tools it works. 
All remaining clients are online and receiving other bits via SCCM but only the TS is not working. I did already an agent repair, but no success. The clients haven't got maintenance windows...

Any hints? It's very confusing for me.

Best Regards,
Sebastian

Hi there,

We are experiencing extreme slowness on our network and I would like to investigate how many devices are currently downloading patches at a time as the slowness appears to be on the datacentre side of the network and not at the site.

Can anyone point me in either the direction of a report to run on SCCM or how i could see this on the management console.  I would want to see all current connections against all deployments.

Many thanks

Ty