Search the Community

Hi All, Can anybody help. Currently trying to build a HP probook 650 with Win7 x86, however I get the following error message during the task sequence, when it is applying system settings "windows could not configure one or more system components, to install windows restart the computer and restart the installation" The only option is to click OK, computer restarts and then the error message reappears. SCCM was building fine and then just stopped working an this error message keeps occurring. Unable to F8 and Shift F10 to get any additional info Please Help Thanks

Hi all, In all our company uses 8 distribution point and the majority are 2008 R2 domain controllers. About two days ago I have done an inplace upgrade on one server to 2012 R2. The upgrade went mostly without a hitch except for the SCCM DP. The error that I was getting was "access denied" or something along those lines when the site server was attempting to distribute content. So I have tried a lot of things so far to the point where I decided to remove the distribution point and start over. No Joy... I am getting an error on the distribution point in the SCCM console stating "Failed to verify the disk drive". when looking further into the distmgr.log, nothing makes sense to me. please see the below log. ~Sleep 60 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:35.310-600><thread=5576 (0x15C8)> ~Sleep 60 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:44.178-600><thread=5576 (0x15C8)> Upgrading DP with ID 18. Thread 0x1e1c. Used 1 threads out of 5. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.248-600><thread=5868 (0x16EC)> ~Processing 18.INS $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.253-600><thread=7708 (0x1E1C)> ~DPID 18 - NAL Path ["Display=\\[sERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[sERVER NAME HERE]\ , ServerName = [sERVER NAME HERE], DPDrive = E:, IsMulticast = 0, PXE = 0, RemoveWDS = 0 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.263-600><thread=7708 (0x1E1C)> Sleep 20 minutes... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.255-600><thread=5868 (0x16EC)> ~Created policy provider trigger for ID 18 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.308-600><thread=5860 (0x16E4)> DPConnection::Connect: For [sERVER NAME HERE], logged-on as rondo\sccmpush~ $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:02.712-600><thread=7708 (0x1E1C)> Found notification for package 'RDO00002' $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.263-600><thread=5576 (0x15C8)> Found notification for package 'RDO00003' $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.268-600><thread=5576 (0x15C8)> Sleep 20 minutes... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.302-600><thread=5868 (0x16EC)> ~Package Thread Limit: 3 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.310-600><thread=5576 (0x15C8)> ~Per package Thread Limit: 5 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.315-600><thread=5576 (0x15C8)> ~Retry interval: 30 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.320-600><thread=5576 (0x15C8)> ~DP upgrade thread Limit: 5 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.325-600><thread=5576 (0x15C8)> ~DP upgrade retry interval: 20 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.330-600><thread=5576 (0x15C8)> ~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.360-600><thread=5576 (0x15C8)> Failed to find a valid drive on the distribution point ["Display=\\[sERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[sERVER NAME HERE]\ $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.541-600><thread=7708 (0x1E1C)> ~Starting package processing thread, thread ID = 0x88 (136) $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.919-600><thread=5576 (0x15C8)> DPConnection::Disconnect: For [sERVER NAME HERE], reverted to SYSTEM context~ $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.131-600><thread=7708 (0x1E1C)> user(NT AUTHORITY\SYSTEM) runing application(SMS_DISTRIBUTION_MANAGER) from machine ([sITE SERVER NAME HERE]) is submitting SDK changes from site(RDO) $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.348-600><thread=7708 (0x1E1C)> ~Starting package processing thread, thread ID = 0x2B78 (11128) $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.426-600><thread=5576 (0x15C8)> ~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.434-600><thread=5576 (0x15C8)> STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[sITE SERVER NAME HERE] SITE=RDO PID=3112 TID=11128 GMTDATE=Thu May 01 12:21:05.440 2014 ISTR0="RDO00003" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00003" $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.440-600><thread=11128 (0x2B78)> ~Retrying package RDO00003 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.450-600><thread=11128 (0x2B78)> No action specified for the package RDO00003. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.455-600><thread=11128 (0x2B78)> STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[sITE SERVER NAME HERE] SITE=RDO PID=3112 TID=136 GMTDATE=Thu May 01 12:21:05.440 2014 ISTR0="RDO00002" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00002" $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.440-600><thread=136 (0x88)> ~Retrying package RDO00002 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.469-600><thread=136 (0x88)> No action specified for the package RDO00002. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.476-600><thread=136 (0x88)> Start adding package to server ["Display=\\[sERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[sERVER NAME HERE]\... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.494-600><thread=136 (0x88)> Will wait for 1 threads to end. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.501-600><thread=136 (0x88)> Thread Handle = 00000000000035C0 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.507-600><thread=136 (0x88)> Start adding package to server ["Display=\\[sERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[sERVER NAME HERE]\... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.473-600><thread=11128 (0x2B78)> Attempting to add or update a package on a distribution point. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.501-600><thread=9852 (0x267C)> The distribution point ["Display=\\[sERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[sERVER NAME HERE]\ is not installed or upgraded yet. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.538-600><thread=9852 (0x267C)> Error occurred. Performing error cleanup prior to returning. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.546-600><thread=9852 (0x267C)> ~Failed to install DP files on the remote DP. Error code = 15 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.455-600><thread=7708 (0x1E1C)> ~Drive E: is not valid. Error = 15 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.566-600><thread=7708 (0x1E1C)> STATMSG: ID=2360 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[sITE SERVER NAME HERE] SITE=RDO PID=3112 TID=7708 GMTDATE=Thu May 01 12:21:05.573 2014 ISTR0="["Display=\\[sERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[sERVER NAME HERE]\" ISTR1="[sERVER NAME HERE]" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\[sERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[sERVER NAME HERE]\" $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.573-600><thread=7708 (0x1E1C)> ~Will try again after 20 mins ... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.582-600><thread=7708 (0x1E1C)> Will wait for 1 threads to end. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.522-600><thread=11128 (0x2B78)> Thread Handle = 00000000000029C8 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.612-600><thread=11128 (0x2B78)> Attempting to add or update a package on a distribution point. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.522-600><thread=10028 (0x272C)> DP thread with array index 0 ended. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.124-600><thread=136 (0x88)> DP thread with thread handle 00000000000035C0 and thread ID 9852 ended. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.131-600><thread=136 (0x88)> The distribution point ["Display=\\[sERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[sERVER NAME HERE]\ is not installed or upgraded yet. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.136-600><thread=10028 (0x272C)> Error occurred. Performing error cleanup prior to returning. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.164-600><thread=10028 (0x272C)> DP thread with array index 0 ended. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.198-600><thread=11128 (0x2B78)> DP thread with thread handle 00000000000029C8 and thread ID 10028 ended. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.205-600><thread=11128 (0x2B78)> ~Package RDO00002 does not have a preferred sender. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.645-600><thread=136 (0x88)> The package and/or program properties for package RDO00002 have not changed, need to determine which site(s) need updated package info. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.653-600><thread=136 (0x88)> ~CDistributionSrcSQL::UpdateAvailableVersion PackageID=RDO00002, Version=3, Status=2301 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.659-600><thread=136 (0x88)> ~StoredPkgVersion (3) of package RDO00002. StoredPkgVersion in database is 3. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.687-600><thread=136 (0x88)> ~SourceVersion (3) of package RDO00002. SourceVersion in database is 3. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.694-600><thread=136 (0x88)> STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[sITE SERVER NAME HERE] SITE=RDO PID=3112 TID=136 GMTDATE=Thu May 01 12:21:06.700 2014 ISTR0="Configuration Manager Client Package" ISTR1="RDO00002" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00002" $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.700-600><thread=136 (0x88)> ~Failed to process package RDO00002 after 33 retries, will retry 67 more times $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.711-600><thread=136 (0x88)> ~Exiting package processing thread. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.720-600><thread=136 (0x88)> ~Package RDO00003 does not have a preferred sender. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.721-600><thread=11128 (0x2B78)> The package and/or program properties for package RDO00003 have not changed, need to determine which site(s) need updated package info. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.749-600><thread=11128 (0x2B78)> ~CDistributionSrcSQL::UpdateAvailableVersion PackageID=RDO00003, Version=1, Status=2301 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.757-600><thread=11128 (0x2B78)> ~StoredPkgVersion (1) of package RDO00003. StoredPkgVersion in database is 1. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.784-600><thread=11128 (0x2B78)> ~SourceVersion (1) of package RDO00003. SourceVersion in database is 1. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.790-600><thread=11128 (0x2B78)> STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[sITE SERVER NAME HERE] SITE=RDO PID=3112 TID=11128 GMTDATE=Thu May 01 12:21:06.797 2014 ISTR0="Configuration Manager Client Upgrade Package" ISTR1="RDO00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00003" $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.797-600><thread=11128 (0x2B78)> ~Failed to process package RDO00003 after 33 retries, will retry 67 more times $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.806-600><thread=11128 (0x2B78)> ~Exiting package processing thread. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.814-600><thread=11128 (0x2B78)> Sleep 20 minutes... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:09.311-600><thread=5868 (0x16EC)> ~Package Thread Limit: 3 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.463-600><thread=5576 (0x15C8)> ~Per package Thread Limit: 5 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.469-600><thread=5576 (0x15C8)> ~Retry interval: 30 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.476-600><thread=5576 (0x15C8)> ~DP upgrade thread Limit: 5 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.482-600><thread=5576 (0x15C8)> ~DP upgrade retry interval: 20 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.488-600><thread=5576 (0x15C8)> ~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.509-600><thread=5576 (0x15C8)> ~Sleep 1826 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.517-600><thread=5576 (0x15C8)> Sleep 20 minutes... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:14.320-600><thread=5868 (0x16EC)> ~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:15.544-600><thread=5576 (0x15C8)> ~Sleep 1821 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:15.553-600><thread=5576 (0x15C8)> Sleep 20 minutes... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:19.332-600><thread=5868 (0x16EC)> ~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.581-600><thread=5576 (0x15C8)> ~Sleep 1816 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.589-600><thread=5576 (0x15C8)> ~Sleep 1816 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.732-600><thread=5576 (0x15C8)> ~Sleep 1816 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.872-600><thread=5576 (0x15C8)> So I have two questions, How can I fix this and how do I prevent it from happening to the remainder? Thank you all in advance. Daniel.

Hi, I am hoping someone here has had a similar issue or can at least point me in the right direction to get my clients installing completely with usable components. The environment: SCCM 2012 Current Branch 1606 (5.00.8412.1307) - installed on a single machine (small production environment) Client version on server (5.00.8412.1307) Client computers: Windows 10 - all machines were recently updated to Windows 10, some via a SCCM TS, others via a USB SCCM TS. In either case, the same image was used. The problem: Newly installed machines are not receiving a usable SCCM client. The CCM clients are reporting in to the MP, but if you attempt to run any action or component, or send any distribution to the machine - you receive a failure. Using Right Click Tools, I generate the "SCCM-error-RCT.jpg" message. If you run the action on the local client, I receive an "The selected cycle cannot start." popup. (SCCM-Client.png) First attempt to resolve is to repair the client - did not work. Reinstalling the client also did not work. Uninstalling, clearing the CCMsetup & SMS registry keys, rebooting and then reinstalling, did not work. Installing a lower client version (5.00.8325.1000) to force an update, did not work. Installs were down as push installs, as local EXE, as local MSI. All installs were with /forceinstall and predefined SMS site code and MP parameters. They were all accepted. In addition - performing the above actions caused a secondary problem: The CCM client is unable to complete its install. The base application installs, but components are not installed (Actions-tab.png & General-tab.png) Going through the logs (CCMSetup.log) I can see that the install is rolling back the installed components. My issue - I cannot see "why" its doing this. Is it rights based? - the client install account has the correct local admin access to the machines, and full access to the \Clients\ folder on the DP Does the system have the needed rights in AD? - yes - it has delegated control to system management and the schema was correctly extended Is the DNS correctly setup? - yes, Ip and names resolve to the correct MP Are Boundaries correct? - I am only using AD defined boundaries and yes, these are correct. Affected machines: 98% of all my machines. If anyone can give me some advice on where to look - I'd greatly appreciate it! Below is an excerpt from the last CCM client deployment to a test machine. Last trial was to install the older client (5.00.8325.1000) through Admin command prompt from a local source folder. ==========[ ccmsetup started in process 848 ]========== ccmsetup 21.09.2016 09.52.14 4208 (0x1070) Updated security on object C:\Windows\ccmsetup\cache\. ccmsetup 21.09.2016 09.52.14 4208 (0x1070) Launch from folder c:\Temp\Current Branch 2012 Client - no updates\ ccmsetup 21.09.2016 09.52.14 4208 (0x1070) CcmSetup version: 5.0.8325.1001 ccmsetup 21.09.2016 09.52.14 4208 (0x1070) Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 21.09.2016 09.52.14 4208 (0x1070) Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 21.09.2016 09.52.14 4208 (0x1070) Running on 'Microsoft Windows 10 Enterprise' (10.0.10586). Service Pack (0.0). SuiteMask = 272. Product Type = 18 ccmsetup 21.09.2016 09.52.14 4208 (0x1070) Ccmsetup command line: ccmsetup.exe /forceinstall SMSSITECODE=SiteCode SMSCACHESIZE=10000 SMSMP=SiteServer ccmsetup 21.09.2016 09.52.14 4208 (0x1070) Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 21.09.2016 09.52.14 4208 (0x1070) Command line: ccmsetup.exe /forceinstall SMSSITECODE=SiteCode SMSCACHESIZE=10000 SMSMP=SiteServer ccmsetup 21.09.2016 09.52.14 4208 (0x1070) SslState value: 224 ccmsetup 21.09.2016 09.52.14 4208 (0x1070) No version of the client is currently detected. ccmsetup 21.09.2016 09.52.14 4208 (0x1070) Task 'Configuration Manager Client Retry Task' does not exist ccmsetup 21.09.2016 09.52.14 4208 (0x1070) Updated security on object C:\Windows\ccmsetup\. ccmsetup 21.09.2016 09.52.15 4208 (0x1070) Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 21.09.2016 09.52.15 4208 (0x1070) Params to send '5.0.8325.1001 Deployment Error: 0x0, ' ccmsetup 21.09.2016 09.52.15 4208 (0x1070) A Fallback Status Point has not been specified and no client was installed. Message with STATEID='100' will not be sent. ccmsetup 21.09.2016 09.52.15 4208 (0x1070) Failed to send status 100. Error (87D00215) ccmsetup 21.09.2016 09.52.15 4208 (0x1070) Successfully deleted existing ccmsetup.exe ccmsetup 21.09.2016 09.52.16 4208 (0x1070) Downloading file c:\Temp\Current Branch 2012 Client - no updates\ccmsetup.exe ccmsetup 21.09.2016 09.52.16 4208 (0x1070) Downloading c:\Temp\Current Branch 2012 Client - no updates\ccmsetup.exe to C:\Windows\ccmsetup\ccmsetup.exe ccmsetup 21.09.2016 09.52.16 4208 (0x1070) File download 14% complete (262144 of 1790136 bytes). ccmsetup 21.09.2016 09.52.16 4208 (0x1070) File download 29% complete (524288 of 1790136 bytes). ccmsetup 21.09.2016 09.52.16 4208 (0x1070) File download 43% complete (786432 of 1790136 bytes). ccmsetup 21.09.2016 09.52.16 4208 (0x1070) File download 58% complete (1048576 of 1790136 bytes). ccmsetup 21.09.2016 09.52.16 4208 (0x1070) File download 73% complete (1310720 of 1790136 bytes). ccmsetup 21.09.2016 09.52.16 4208 (0x1070) File download 87% complete (1572864 of 1790136 bytes). ccmsetup 21.09.2016 09.52.16 4208 (0x1070) File download 100% complete (1790136 of 1790136 bytes). ccmsetup 21.09.2016 09.52.16 4208 (0x1070) Download complete. ccmsetup 21.09.2016 09.52.16 4208 (0x1070) Successfully created the ccmsetup service ccmsetup 21.09.2016 09.52.21 4208 (0x1070) ==========[ ccmsetup started in process 3376 ]========== ccmsetup 21.09.2016 09.52.22 4888 (0x1318) Updated security on object C:\Windows\ccmsetup\cache\. ccmsetup 21.09.2016 09.52.22 4888 (0x1318) Launch from folder C:\Windows\ccmsetup\ ccmsetup 21.09.2016 09.52.22 4888 (0x1318) CcmSetup version: 5.0.8325.1001 ccmsetup 21.09.2016 09.52.22 4888 (0x1318) Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 21.09.2016 09.52.22 4888 (0x1318) Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 21.09.2016 09.52.22 4888 (0x1318) Successfully started the ccmsetup service ccmsetup 21.09.2016 09.52.22 4208 (0x1070) In ServiceMain ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Folder 'Microsoft\Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Failed to connect to policy namespace. Error 0x8004100e ccmsetup 21.09.2016 09.52.22 4208 (0x1070) Failed to revoke client upgrade local policy. Error 0x8004100e ccmsetup 21.09.2016 09.52.22 4208 (0x1070) Deleted file C:\Windows\ccmsetup\ccmsetup.exe.download ccmsetup 21.09.2016 09.52.22 4208 (0x1070) Task 'Configuration Manager Client Upgrade Task' does not exist ccmsetup 21.09.2016 09.52.22 4208 (0x1070) CcmSetup is exiting with return code 0 ccmsetup 21.09.2016 09.52.22 4208 (0x1070) Running on 'Microsoft Windows 10 Enterprise' (10.0.10586). Service Pack (0.0). SuiteMask = 272. Product Type = 18 ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /source:"c:\Temp\Current Branch 2012 Client - no updates" "/forceinstall" "SMSSITECODE=SiteCode" "SMSCACHESIZE=10000" "SMSMP=SiteServer" ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /source:"c:\Temp\Current Branch 2012 Client - no updates" "/forceinstall" "SMSSITECODE=SiteCode" "SMSCACHESIZE=10000" "SMSMP=SiteServer" ccmsetup 21.09.2016 09.52.22 1588 (0x0634) SslState value: 224 ccmsetup 21.09.2016 09.52.22 1588 (0x0634) CCMHTTPPORT: 80 ccmsetup 21.09.2016 09.52.22 1588 (0x0634) CCMHTTPSPORT: 443 ccmsetup 21.09.2016 09.52.22 1588 (0x0634) CCMHTTPSSTATE: 224 ccmsetup 21.09.2016 09.52.22 1588 (0x0634) CCMHTTPSCERTNAME: ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Lookup MP: SiteServer ccmsetup 21.09.2016 09.52.22 1588 (0x0634) FSP: ccmsetup 21.09.2016 09.52.22 1588 (0x0634) CCMFIRSTCERT: 1 ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Config file: ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Retry time: 10 minute(s) ccmsetup 21.09.2016 09.52.22 1588 (0x0634) MSI log file: C:\Windows\ccmsetup\Logs\client.msi.log ccmsetup 21.09.2016 09.52.22 1588 (0x0634) MSI properties: SMSSITECODE="SiteCode" SMSCACHESIZE="10000" SMSMP="SiteServer" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" SMSSLP="SiteServer" CCMFIRSTCERT="1" ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Source List: ccmsetup 21.09.2016 09.52.22 1588 (0x0634) c:\Temp\Current Branch 2012 Client - no updates ccmsetup 21.09.2016 09.52.22 1588 (0x0634) MPs: ccmsetup 21.09.2016 09.52.22 1588 (0x0634) None ccmsetup 21.09.2016 09.52.22 1588 (0x0634) No version of the client is currently detected. ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Task 'Configuration Manager Client Retry Task' does not exist ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Updated security on object C:\Windows\ccmsetup\. ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Params to send '5.0.8325.1001 Deployment Error: 0x0, ' ccmsetup 21.09.2016 09.52.22 1588 (0x0634) A Fallback Status Point has not been specified and no client was installed. Message with STATEID='100' will not be sent. ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Failed to send status 100. Error (87D00215) ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Detected 105754 MB free disk space on system drive. ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Client OS Version 6.2 Service Pack 0.0 ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Failed to get UWF_Filter instance. UWF Feature not installed. HRESULT=0x80041010 ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Running as user "SYSTEM" ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Checking Write Filter Status. ccmsetup 21.09.2016 09.52.22 1588 (0x0634) This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 21.09.2016 09.52.22 1588 (0x0634) Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=SiteCode))' ccmsetup 21.09.2016 09.52.23 1588 (0x0634) OperationalXml '<ClientOperationalSettings><Version>5.00.8412.1307</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>224</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers></CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202EF308201D7A00302010202105A31A88AAEF19AB84601CE2604217FB7300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3136303630313037333534355A180F32313136303530393037333534355A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A0282010100DBA6E68CE03ADCF273A8B20BA8729C367C14904FAEBCC6C8A7DFDDAF41EBE1D277F53625B776C88DFA0A95AA4CF1354978F2F3CF6F2F78753A91D156849C20548BEA51EBC9DD40CFE626F998AD64E5AD35057C5FF61FA0E52616E6EC3A2C4EF8BE3EC720189AE891AE8623B017CF714915E559A5B347E1B9006B962DFCDEB594B1D8E2C4339DF581243D68A901A0860A2016F515D60F8BD199188FB0699394C56D84F20275AADE1105AAA55E1093004A557CCD569FF22CA34F926DAD1B196603A263A1E1CED9BA8383CC8A99EB8A001956A78E8649371905269BD17E0DFD183319C1B2220E6E97C29EE228577A49CCD980EC09849A134123585469071B6BEF6D0203010001A3373035301D0603551D110416301482126B672D7363636D30312E6B672E6C6F63616C30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B0500038201010046359CD1D5D90C32640FA5FEA36238A92F68DF6DA6A3ED3CCB2F9D250E7E2CA57ACBA317D3C5EB7EC7E4BD4410B60E5A7BFF1944B267FF08668580D2A7B9F524F74F27197856D939A6CF958A707DAECB2D31AD1F2F765F125B3C19DC92EF44D033F0AD490BBCF2A56734A6FD1926F8F2B5EF0F6D7DE1107505CD27CCF97EE02EA00D5C24106C2254F63269D654789E58ED61440347C67E77C08BE8AF1C298CA82558E81D6136A43B83402215C4AAC1B081E4C08025E6C266F9AD804932C94233E0B9DC19872A4EEC3E990349FEE01840AB46ADDA36EC19EFA07499F158E0CEAF4C370AEB8B2F8BF9DF1355BA920DB3DDB77DDEE1C0B486B1B92C6BFC44EE99A4</SiteSigningCert></SecurityConfiguration><RootSiteCode>SiteCode</RootSiteCode><CCM> <CommandLine>SMSSITECODE=SiteCode SMSCACHESIZE=10000 SMSMP=SiteServer</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSLState" Value="0" /></Capabilities><Domain Value="kg.local" /><Forest Value="kg.local" /></ClientOperationalSettings>' ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) The MP name retrieved is 'SiteServer' with version '8412' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>' ccmsetup 21.09.2016 09.52.23 1588 (0x0634) MP 'SiteServer' is compatible ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Retrieved 1 MP records from AD for site 'SiteCode' ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Retrived site version '5.00.8412.1307' from AD for site 'SiteCode' ccmsetup 21.09.2016 09.52.23 1588 (0x0634) SiteCode: SiteCode ccmsetup 21.09.2016 09.52.23 1588 (0x0634) SiteVersion: 5.00.8412.1307 ccmsetup 21.09.2016 09.52.23 1588 (0x0634) No MPs were specified from commandline or the mobileclient.tcf. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Downloading file ccmsetup.cab ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Determining source location... ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Found accessible source: c:\Temp\Current Branch 2012 Client - no updates ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Found available source c:\Temp\Current Branch 2012 Client - no updates\ ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Downloading c:\Temp\Current Branch 2012 Client - no updates\ccmsetup.cab to C:\Windows\ccmsetup\ccmsetup.cab ccmsetup 21.09.2016 09.52.23 1588 (0x0634) File download 100% complete (9745 of 9745 bytes). ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Deleted file C:\Windows\ccmsetup\ccmsetup.cab ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Download complete. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Ccmsetup.cab manifest has been changed. Force to download client.msi and necessary pre-reqs again. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) C:\Windows\ccmsetup\ccmsetup.cab is Microsoft trusted. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Successfully extracted manifest file C:\Windows\ccmsetup\ccmsetup.xml from file C:\Windows\ccmsetup\ccmsetup.cab. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Loading manifest file: C:\Windows\ccmsetup\ccmsetup.xml ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Successfully loaded ccmsetup manifest file. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Checking if manifest version '5.00.8325.1000' is newer than the ccmsetup version '5.0.8325.1001' ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Running from temp downloaded folder or manifest is not newer than ccmsetup. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/vcredist_x86.exe' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'x64/vcredist_x64.exe' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/vc50727_x86.exe' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'x64/vc50727_x64.exe' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/WindowsUpdateAgent30-x86.exe' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'x64/WindowsUpdateAgent30-x64.exe' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/msxml6.msi' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'x64/msxml6_x64.msi' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/msrdcoob_x86.exe' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'x64/msrdcoob_amd64.exe' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'pkgmgr.exe' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'dism.exe' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'wimgapi.msi' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/MicrosoftPolicyPlatformSetup.msi' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'x64/MicrosoftPolicyPlatformSetup.msi' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/WindowsFirewallConfigurationProvider.msi' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'x64/WindowsFirewallConfigurationProvider.msi' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/Silverlight.exe' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/wic_x86_enu.exe' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'x64/wic_x64_enu.exe' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/NDP452-KB2901907-x86-x64-AllOS-ENU.exe' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'SCEPInstall.exe' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'i386/client.msi' is not applicable. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Item 'x64/client.msi' is applicable. Add to the list. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Default CSP is Microsoft Enhanced RSA and AES Cryptographic Provider ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Default CSP Type is 24 ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Discovering whether item 'i386/vcredist_x86.exe' exists. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Detected item 'i386/vcredist_x86.exe' ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Discovering whether item 'x64/vcredist_x64.exe' exists. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Detected item 'x64/vcredist_x64.exe' ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Discovering whether item 'x64/vc50727_x64.exe' exists. ccmsetup 21.09.2016 09.52.23 1588 (0x0634) Upgrade code '{A8D19029-8E5C-4E22-801

Hi, I've ran into a bit of an issue which I hope someone can assist (or point me in the right direction) My building had SCCM installed and was the only site in the company. We recently acquired another company and they had the newest SCCM environment so the decision was made to have them as the main site and set us up as a DP. The DP was setup here and everything was setup and was looking great, I ran the below script (with the correct site name) and it worked fine, the machines picked up the new site code and were showing in "new" Configuration Manager Console. On Error Resume Next set oSMSClient = CreateObject ("Microsoft.SMS.Client") if Err.Number <>0 then wscript.echo "Could not create SMS Client Object - quitting" end if 'Assign client to Servername oSMSClient.SetAssignedSite "SITECODE",0 set oSMSClient=nothing The last couple of days, when i add machines, they are no longer being picked up by the new Configuration Manager Console. They pick up the site code and the assigned management point but are not being seen in the new Configuration Manager Console. Below is the log from exermgr.log Raising event: [SMS_CodePage(850), SMS_LocaleID(2057)] instance of SoftDistProgramCompletedSuccessfullyEvent { AdvertisementId = "XXX200AC"; ClientID = "GUID:XXX"; DateTime = "20170504115048.531000+000"; MachineName = "XXX"; PackageName = "XXX002DC"; ProcessID = 4864; ProgramName = "SiteCode_Change"; SiteCode = "XXX"; ThreadID = 1712; UserContext = "NT AUTHORITY\\SYSTEM"; }; execmgr 04/05/2017 12:50:48 1712 (0x06B0) Raised Program Success Event for Ad:XXX200AC, Package:XXX002DC, Program: SiteCode_Change execmgr 04/05/2017 12:50:48 1712 (0x06B0) Execution is complete for program SiteCode_Change. The exit code is 0, the execution status is Success execmgr 04/05/2017 12:50:48 1712 (0x06B0) I have checked boundrys and the network team have said they haven't changed anything so I'm a bit perplexed. Any help appreciated. Paul

Hey Guys / Niall - I'm wrapping up a complete rebuild of the production environment's SCCM. So far, I've installed SCCM 2012 R2, applied SP1, then applied CU3. Recently, I installed MDT 2013 Update 2 then ran the ConfigMgr Integration as Administrator. I'm trying to create the base MDT Packages, but am getting errors! When trying to create a new MDT Boot Image, I perform the following steps: Right click Boot image and choose to create a new MDT boot image Enter the (empty) source path for the boot image Enter the desired name and version Select x64 and 128mb On the next page (Components) get the error message "The path is not of a legal form" The components page behind it is empty (doesn't list any of the components). Clicking OK simply dismisses the error window and leaves me at the blank Components page. If i click OK on it, I get the error "Object reference not set to an instance of an object" so must cancel out of it. As I initially installed MDT to D: (keeping the rest of the default path the same), I removed the ConfigMgr integration, uninstalled MDT, reinstalled MDT to the default path on C:, reintegrated, and tried again - got the same error. Google only has a couple of things about it - one being from Niall - saying basically to make sure everything is launched as admin. It is, but still no go. Any suggestions? Thanks!

Hi All, We are currently using SCCM 2012 and are having problems getting the task sequence to create a local admin account. we used the below as a run command which doesn't work @echo off cls echo Creating Local Account: mccuser pushd %~dp0 echo. net user user PAssword /ADD /FULLNAME:"mccuser" /COMMENT:"Built in Local Admin Account" /ACTIVE:YES /PASSWORDCHG:NO /EXPIRES:NEVER net localgroup "Administrators" user /add wmic useraccount where "name='user'" set PasswordExpires=False popd We also created the below as a batch file and tried that in the task sequence as a application, again this does not work. cd\ mkdir .\User net user User Password /ADD net localgroup administrators %computername%\User /add rmdir .\User Both of the above work when run but not when part of a task sequence. Please can anybody tell us how you can get a command in the task sequence that will create a local admin account. Cheers

Hi All I am stuck with a problem in SCCM 2012. It is unable to distribute newly packaged content. The DP just says "starting to process content" and doesnt change. I have removed the DP from the server and re-added it. Reinstalled IIS Recreated the package(s) Installed update http://support.microsoft.com/kb/2854009 I still have the issue, All the distmgr.log file says it "Package is already in the queue" One thing to note: I tested the DP by removing the SMSPKG (driveletter) $ share, but recreating the DP does not re-create this share. This started mid July, no SCEP definitions are currently being deployed. All work has been done on the Primary Site server, the data for the packages are also stored on this server. Version 5.00.7804.1000 Build number 7804 Thank you Morne

Hi! We have a number of computer models that we image with SCCM 2012 R2, and everything works just fine, apart from one model: Novatech nSpire 15.6 (yeah, the model is not descriptive, but that is the model name!) The laptop has standard Intel Haswell hardware, one fixed disk (Sandisk SSD) and an optical drive. This is much like other computers that we have in the organisation and we have no computers with two or more fixed disks When we image this particular model of computer, the task sequence fails at the "Apply Operating System Image". The partition map from the task sequence is: Volume 1: 350MB fixed size, NTFS Volume 2: 100% remaining space, NTFS The operating system is deployed to the "next available formatted partition" The SSD is partitioned and formatted successfully during the task sequence. If I disable this step and use diskpart for this, the task sequence still fails! Below is the point of failure, from the smsts.log file: User did not specify local data drive TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume C:\ has 336084992 bytes of free space TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume C:\ is not bootable TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume D:\ has 127548887040 bytes of free space TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume D:\ is not bootable TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume E:\ is not a fixed hard drive TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume F:\ is not a fixed hard drive TSManager 15/10/2014 10:42:51 1292 (0x050C) Volume X:\ is not a fixed hard drive TSManager 15/10/2014 10:42:51 1292 (0x050C) TSM root drive = TSManager 15/10/2014 10:42:51 1292 (0x050C) We do not find an available volume to store the local data path TSManager 15/10/2014 10:42:51 1292 (0x050C) Set a global environment variable _SMSTSNextInstructionPointer=11 TSManager 15/10/2014 10:42:51 1292 (0x050C) Set a TS execution environment variable _SMSTSNextInstructionPointer=11 TSManager 15/10/2014 10:42:51 1292 (0x050C) Set a global environment variable _SMSTSInstructionStackString=10 TSManager 15/10/2014 10:42:51 1292 (0x050C) Set a TS execution environment variable _SMSTSInstructionStackString=10 TSManager 15/10/2014 10:42:51 1292 (0x050C) Save the current environment block TSManager 15/10/2014 10:42:51 1292 (0x050C) pszPath[0] != L'\0', HRESULT=80070057 (e:\nts_sccm_release\sms\framework\core\ccmcore\path.cpp,60) TSManager 15/10/2014 10:42:51 1292 (0x050C) Filesystem::Path::Add(sEnvPath, EnvDataFileName, sEnvPath), HRESULT=80070057 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,676) TSManager 15/10/2014 10:42:51 1292 (0x050C) Failed to save environment to (80070057) TSManager 15/10/2014 10:42:51 1292 (0x050C) TS::Environment::SharedEnvironment.saveEnvironment(szPath), HRESULT=80070057 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\executionenv.cxx,842) TSManager 15/10/2014 10:42:51 1292 (0x050C) Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance. The parameter is incorrect. (Error: 80070057; Source: Windows) TSManager 15/10/2014 10:42:51 1292 (0x050C) SaveEnvironment(), HRESULT=80070057 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\executionenv.cxx,420) TSManager 15/10/2014 10:42:51 1292 (0x050C) Failed to persist execution state. Error 0x(80070057) TSManager 15/10/2014 10:42:51 1292 (0x050C) Failed to save execution state and environment to local hard disk TSManager 15/10/2014 10:42:51 1292 (0x050C) Any help in this would be greatly appreciated! -- Matt

Hello Folks, Long time Windows Noob fan, first time poster... I have a question about a Task Sequence in SCCM with MDT... So when creating a TS via MDT, you'll have that nice wizard that helps you out and I could not find anything that would define when to create a new XYZ Package and when to reuse it or not reuse it in another SCCM MDT Task Sequence... Create MDT Task Sequence > Boot Image Step > you have a choice to use an existing one or create a new one... Since I only have the stock SCCM Boot images, i do want to make an MDT boot image for x86 and x64... - Can I use these MDT Boot Images for another TS, if yes, when would i want to create another set of MDT Boot Images x86 and x64? Create MDT Task Sequence > MDT Package Step > you have a choice to use an existing or create a new one. When you create a new one, the folders at the given UNC Path look like as if it is a new deployment share which you would use for WorkBench. - Can I use this MDT Package for another TS, if yes, when would i want to create another set of MDT Packages? Also, what is the best practices for naming convention or organization? Create MDT Task Sequence > CustomSettings.ini Step > again, you have a choice to use an existing or create a new one. Since i dont have one, i'd create a new one but when would you want to reuse it and when would you want to create a brand new one? For all 3, i feel like if i make a new anything, i should make a new folder though i'm not quite sure what the best folder plan is for organization would be. Thank you for any help, i really do appreciate it!

Hello Everyone! I'm very new to SCCM 2012, so please explain detailed as possible. I'd like to deploy Visual Studio 2012 using SCCM 2012 (which was downloaded from MSDN). I've being trying to search the internet and Windows-Noob web, but i couldn't find instructions to deploy it. I've only find articles on VS2010 or SCCM 2007 (for example microsoft's msdn: http://msdn.microsoft.com/en-us/library/ee225239.aspx ) which wasn't understandable enough. I'm familiar with creating other applications (mostly msi based) and deploying them as a push installations and as a part of a complete task sequence of installing new computer, but i don't how to install visual studio 2012 with SCCM 2012. I'll be grateful if someone will be kind and write me general step by step post on deploying VS2012 with SCCM 2012. Thank you very much, David.

Hi everyone, I am trying to capture a windows 8.1 64 bit image with Office 2013, citrix and a few other apps installed. I've also tried on a windows 7 32 bit image with the same result. The result is I can create the iso file. When I mount the ISo file on the reference machine I can run the wizard and point to a location to create the wim file. When I click Finish nothing happens. I've tried multiple times and different machines with the same results. The machines are not on the domain. Any suggestions? Thanks in advance.

I work at a community college and we have sccm clients running Office versions from 2003-2013. I have scoured the web trying to find a query that could accomplish this task, but with my lack of SQL knowledge and specificity of the statement, I couldn't find a solution. Any thoughts?

Since upgrading to 2012 R2 SP1 I've noticed that memory usage will steadily climb on my site server to the point that after a couple days, I am unable to connect with the console or log into the server and have to do a hard reboot. The process that is sucking up all the memory is SMSEXEC.EXE. Before the SP1 upgrade this didn't happen. Is anyone else seeing something similar?

hi SCCM guys Any idea how to disable IPv6 via task sequence ? I have requremnt my enviroemnt that before domin join step need to disable IPv6 to avoid system look for diffent DNS server Or is there anyway I can set diffent IPv6 DNS server?

Need help to narrow down the issue...I get this error in netsetup.log as the PC is unable to join domain after the t/s is run

Hello community, I just want to share a strange behavior I'm experiencing when creating a USB standalone media for Windows 8.1 TS. Actually, I receive an error when I try to generate the USB Stick, the wizard says: "Media creation failed with error message: 'The system cannot find the path specified' Refer to CreateTsMedia.log file to find more details The only error reported in the log file is: =========================================== Beginning pass to compute volume layout =========================================== Setting up new volume WriteVolumeId() Failed to create media CreateTsMedia failed with error 0x80070003, details='' MediaGenerator::~MediaGenerator() Media creation process that was started from Admin Console completed. CreateMedia.exe finished with error code 80070003 So almost nothing is written on the disk, but error details obviously can't help me. It is strange because when I'm generating Windows 7 standalone media (with the same USB stick, on the same computer), I have no issue at all. I searched for fixes related to this error code on the web, but none of the method helps (unmounting network drives, assigning a drive letter to hidden partitions [i'm running W8.1], making sure I have enough disk space on my computer, upgrading the SCCM console... I even tried Voodoo it didn't help as well...) SCCM Version is 2012 R2 CU4. I'm running the console as domain admin. Any advice is welcome Thanks!

Hi, We restored our site onto a server with a different disk layout. Everything appears to be working other than the site status display. The status for the Site Server and Application Catalog website point are always critical and the Storage Object points to the old (wrong) location. Does anyone know how this can be updated to be correct? It would probably be possible by directly editing the SQL database but I know this is not supported. thanks.

Hello, I am getting ready to deploy some Office Service Packs. However I have no service packs for Microsoft Project 2013 or Visio 2013. Google search shows that these service packs are available however I cannot for the life of me find these in WSUS/SCCM Software Updates. I see SPs for Windows, Office, Visio Viewer, SharePoint, etc so the classification is definitely being polled and added to SCCM. Do these two (Project/Visio) service packs need to be pushed out as packages? If anyone could shed some light on this it'd be much appreciated. Thanks, Mike

Hi Forum, Please help! Here's the story. When we had our SCCM installed it seems that some bright spark decided to put a trial version of SQL on the server its installed on. Last week the trial ran out and reporting stopped and then no one could connect via the consoles. Our apps team fixed this and we can now log into SCCM 2012 but we cannot build any machines via PXE. Any suggestions? I've checked the SMSPXE.log and see errors: Loaded D:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 24/03/2015 10:36:17 8428 (0x20EC) Opening image file D:\RemoteInstall\SMSImages\MON0006E\winpe8.MON0006E.wim SMSPXE 24/03/2015 10:36:17 8428 (0x20EC) Found Image file: D:\RemoteInstall\SMSImages\MON0006E\winpe8.MON0006E.wim PackageID: MON0006E ProductName: Microsoft® Windows® Operating System Architecture: 0 Description: Microsoft Windows PE (x86) Version: Creator: SystemDir: WINDOWS SMSPXE 24/03/2015 10:36:17 8428 (0x20EC) Closing image file D:\RemoteInstall\SMSImages\MON0006E\winpe8.MON0006E.wim SMSPXE 24/03/2015 10:36:17 8428 (0x20EC) Failed adding image D:\RemoteInstall\SMSImages\MON0006E\winpe8.MON0006E.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 24/03/2015 10:36:17 8428 (0x20EC) Loaded D:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Opening image file D:\RemoteInstall\SMSImages\MON00004\boot.MON00004.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Found Image file: D:\RemoteInstall\SMSImages\MON00004\boot.MON00004.wim PackageID: MON00004 ProductName: Microsoft® Windows® Operating System Architecture: 0 Description: Microsoft Windows PE (x86) Version: Creator: SystemDir: WINDOWS SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Closing image file D:\RemoteInstall\SMSImages\MON00004\boot.MON00004.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Failed adding image D:\RemoteInstall\SMSImages\MON00004\boot.MON00004.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Loaded D:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Opening image file D:\RemoteInstall\SMSImages\MON00005\boot.MON00005.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Found Image file: D:\RemoteInstall\SMSImages\MON00005\boot.MON00005.wim PackageID: MON00005 ProductName: Microsoft® Windows® Operating System Architecture: 9 Description: Microsoft Windows PE (x64) Version: Creator: SystemDir: WINDOWS SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Closing image file D:\RemoteInstall\SMSImages\MON00005\boot.MON00005.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Failed adding image D:\RemoteInstall\SMSImages\MON00005\boot.MON00005.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Loaded D:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Opening image file D:\RemoteInstall\SMSImages\MON00006\WinPE.MON00006.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Found Image file: D:\RemoteInstall\SMSImages\MON00006\WinPE.MON00006.wim PackageID: MON00006 ProductName: Microsoft® Windows® Operating System Architecture: 0 Description: Microsoft Windows PE (x86) Version: Creator: SystemDir: WINDOWS SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Closing image file D:\RemoteInstall\SMSImages\MON00006\WinPE.MON00006.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Failed adding image D:\RemoteInstall\SMSImages\MON00006\WinPE.MON00006.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Loaded D:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Opening image file D:\RemoteInstall\SMSImages\MON00007\WinPE.MON00007.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Found Image file: D:\RemoteInstall\SMSImages\MON00007\WinPE.MON00007.wim PackageID: MON00007 ProductName: Microsoft® Windows® Operating System Architecture: 9 Description: Microsoft Windows PE (x64) Version: Creator: SystemDir: WINDOWS SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Closing image file D:\RemoteInstall\SMSImages\MON00007\WinPE.MON00007.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Failed adding image D:\RemoteInstall\SMSImages\MON00007\WinPE.MON00007.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Loaded D:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Opening image file D:\RemoteInstall\SMSImages\MON0000E\winpe.MON0000E.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Found Image file: D:\RemoteInstall\SMSImages\MON0000E\winpe.MON0000E.wim PackageID: MON0000E ProductName: Microsoft® Windows® Operating System Architecture: 0 Description: Microsoft Windows PE (x86) Version: Creator: SystemDir: WINDOWS SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Closing image file D:\RemoteInstall\SMSImages\MON0000E\winpe.MON0000E.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Failed adding image D:\RemoteInstall\SMSImages\MON0000E\winpe.MON0000E.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Loaded D:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Opening image file D:\RemoteInstall\SMSImages\MON0000F\winpe.MON0000F.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Found Image file: D:\RemoteInstall\SMSImages\MON0000F\winpe.MON0000F.wim PackageID: MON0000F ProductName: Microsoft® Windows® Operating System Architecture: 9 Description: Microsoft Windows PE (x64) Version: Creator: SystemDir: WINDOWS SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Closing image file D:\RemoteInstall\SMSImages\MON0000F\winpe.MON0000F.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Failed adding image D:\RemoteInstall\SMSImages\MON0000F\winpe.MON0000F.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Loaded D:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Opening image file D:\RemoteInstall\SMSImages\MON00010\winpe.MON00010.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Found Image file: D:\RemoteInstall\SMSImages\MON00010\winpe.MON00010.wim PackageID: MON00010 ProductName: Microsoft® Windows® Operating System Architecture: 0 Description: Microsoft Windows PE (x86) Version: Creator: SystemDir: WINDOWS SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Closing image file D:\RemoteInstall\SMSImages\MON00010\winpe.MON00010.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Failed adding image D:\RemoteInstall\SMSImages\MON00010\winpe.MON00010.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Loaded D:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Opening image file D:\RemoteInstall\SMSImages\MON00011\winpe.MON00011.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Found Image file: D:\RemoteInstall\SMSImages\MON00011\winpe.MON00011.wim PackageID: MON00011 ProductName: Microsoft® Windows® Operating System Architecture: 9 Description: Microsoft Windows PE (x64) Version: Creator: SystemDir: WINDOWS SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Closing image file D:\RemoteInstall\SMSImages\MON00011\winpe.MON00011.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Failed adding image D:\RemoteInstall\SMSImages\MON00011\winpe.MON00011.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Loaded D:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Opening image file D:\RemoteInstall\SMSImages\MON0006E\winpe8.MON0006E.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Found Image file: D:\RemoteInstall\SMSImages\MON0006E\winpe8.MON0006E.wim PackageID: MON0006E ProductName: Microsoft® Windows® Operating System Architecture: 0 Description: Microsoft Windows PE (x86) Version: Creator: SystemDir: WINDOWS SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Closing image file D:\RemoteInstall\SMSImages\MON0006E\winpe8.MON0006E.wim SMSPXE 24/03/2015 10:38:17 8428 (0x20EC) Failed adding image D:\RemoteInstall\SMSImages\MON0006E\winpe8.MON0006E.wim. Will Retry.. Unspecified error (Error: 80004005; Source: Windows) SMSPXE 24/03/2015 10:38:17 8428 (0x20EC)

Hi guys, I was hoping someone could provide some guidance. We are currently in the process of a forest/domain consolidation. We have two AD forests with one domain in each. We are in the process of standing up a third forest with one domain in it on 2012 R2 that we will be moving all resources and users to over the next year. I understand that i'll need to bring up a new primary site with a new Site Code in the new third forest/domain. Some other details about the SCCM 2007 environment: One Site Server running SCCM 2007 R3 One Remote SQL server running 2008 Forefront Endpoint Protection is Integrated WSUS with a remote WSUS server on 3.0 is integrated Windows OS Deployments with WIndows Deployment Services are integrated and currently configured for deploying Windows 7 Parallels Management Suite for Managing Macs is integrated We are currently deploying many applications via SCCM Updates Publisher 2011 is current integrated with SCCM on the site server. My question is, should i migrate from the existing SCCM 2007 environment to SCCM 2012 whilst still in the same forest first before migrating collections and packages etc to the new forest? Or just migrate once and migrate the SCCM 2007 forest collections and packages etc to the new 2012 R2 forest so as to not do double work? Any pros and cons either way? If anyone has done this sort of migration i would appreciate your recommendations. Thanks Joey

Hi All, Trying to build and capture a VM machine. Created a collection, however when trying to build and capture I get the following error 0x00000037 Please can anyone help, I've checked the internet and cant find anything to help. Cheers

Greetings All, I am having a bit of trouble creating a TS that creates two partitions. If I only have one it works perfectly as soon as I try and add the second the TS fails. I can see what is causing the failure but i don't know why. Let me know if any other info is needed. Desired Outcome: Windows 7 with two partitons C: and D: (system and data respectively) <-- This part does actually occur. But I end up with a partially imaged machine. Partition TS Step: The Cause: The _SMSTaskSequence folder gets placed on D: then after the step below occurs it starts looking for the TS files to be on E: which doesn't exist. (Full log attached) Cheers, Mike smsts.log

I am planning my upgrade to R2 and had some questions. We are integrated with MBAM 2.5 and MDT update 1. Do I need to remove the integration before updating or can I just update to R2 on top of MDT and MBAM? Thanks.

Just wondering what permissions does these SCCM 2012's service accounts need EXACTLY, for example: ClientInst = Local Administrator on site computers Network Access Account = ?? What permissions on the file server source?! Domain Join = ?? What permissions, where and how to set these? SQL Service account = ?? SCCM Admin = ?? What and where Definitive list would be good... also looking for some kind of guide for SCCM 2012 Delta Group Policy, how to set the user rights assignments right and so on... Thx in advance.

I'm using SUP to deploy IE9 to my clients. This should be straightforward. I created a software update package and deployed it to a collection. SCCM 2012 is showing that these clients are compliant, but on the clients IE9 is not there even after a reboot. I've attached two screens showing that the clients are showing they're indeed compliant and the software installed with success. IE 9 is not on any of those machines though. I've watched logs, and not seeing any errors (probably because it's showing updated). On one machine I tried to update Windows from the internet, and noticed that IE9 was available. SCCM 2012 is reading it as compliant, but it's obviously not installed. Am I missing something?