Jump to content




Search the Community

Showing results for tags 'sccm'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General Stuff
    • Site News
    • Windows News
    • Suggestion box
    • General Chat
    • Events
    • Jobs
  • Microsoft Deployment Toolkit
    • Deploying Windows 10, Windows 8.1, Windows 7 and more...
  • Cloud
    • Microsoft Intune
    • Azure
    • Office 365
  • SMS, SCCM, SCCM Current Branch, SCCM Technical Preview
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • How do I ?
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Server
    • Active Directory
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Operations Manager
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS
  • Microsoft SQL Server
    • SQL Server
  • Windows General
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • how do I do this ?
    • windows screenshots

Found 543 results

  1. Hi, We are currently looking at deploying windows 10 education 1610 across our corporate network (we are a college). The gold image has been created and successfully deployed to machines however we are finding that there are some drivers missing from the machines on completion. I know that drivers can be added into SCCM as packages to be used in the deployments but since we dont run on a standard model of machine this can become a bit of a laborious process. We noted that when you install a standard version of windows in a non corporate environment, windows will try to find drivers for unknown devices via windows update. Obviously updates within the network are controlled by SCCM but what we want to be in a situation where a machine is imaged and then windows update searches for any missing drivers. We have updated the configuration of the updates within SCCM to include updates for windows 10 and servicing to hopefully enable this (see the below images). I think really we need to know if what we want to do is actually possible within the scope of SCCM or if we are going to have to stick to the classic method of creating and importing numerous driver packages each time we add new hardware to our network. Any advice from the experts would be most useful! Thanks, Simon
  2. Hello guys, I need help, im trying to deploy a Win10 task with SCCM with MDT integrated via PXE in my lab. Everything work fine up until the point the task initiates. Basically what happens is that after downloading the boot image and starting to run the TS after a short while, when the Preparing Network Configuration Screen appears my VirtualBox just reboots and it tries again to download the boot image to run the task again. I´ve searched for a workaround and found one where it basically creates a sleep.vbs to stall for the network configurations to initialize, but still to no avail. Can some help me with this problem pls? Would greatfully apreciate the help Some notes: Both the MDT boot image and the original have the same problem. I´ve Tried with network drivers and without network drivers and still to no avail. I tried to deploy with MDT Task and just a Build an Capture Task it and got the same thing. The Configuration on my VirtualBox on the lan scheme is the Bridged adaptor. I've also tried with VMWare and got the same luck. I disabled the firewall on my machine that has the virtual box. I also created a GPO to enable the UDP ports that PXE uses I tried with 2 different network acess acount and got the same error. While in the machine it as an IP and it can ping my server. The SMSTS.log is in here: https://imgur.com/a/qjvze
  3. Hi, I`m buildiong my refresh task sequence to migrate from WIn7 to Win10, my Online USMT transfers the data, however the printer queue, Wallpaper and Outlook signature don`t get transferred, i`m using the default USMT settings. am I missing something? SCCM 1706 + ADK1703
  4. Introduction Microsoft (together with a bunch of Microsoft MVP's in Seattle) have released the latest Technical Preview release of System Center Configuration Manager namely System Center Configuration Manager Technical Preview 1711. There are two main versions (of Configuration Manager) available: System Center Configuration Manager (Current Branch) System Center Configuration Manager (Technical Preview) System Center Configuration Manager (Current Branch) is designed for use in production, for managing anything from small to very large Enterprises whereas System Center Configuration Manager (Technical Preview) is for lab environments only and is limited to 10 clients. The Technical Preview releases are released monthly, and contain the latest and greatest features being trialed in the product, and usually these new features are the result of feedback from uservoice. Current Branch releases on the other hand are released only a few times per year and contain stable, tested features that are mature enough to release into production environments. System Center Configuration Manager Technical Preview 1711 is now available. This release offers the following new features: Run Task Sequence step – This release includes improvements to the new Run Task Sequence step, which runs another task sequence creating a parent-child relationship between task sequences. See the online documentation for more details about the improvements. This is currently the feature with the third highest number of votes on UserVoice Allow user interaction when installing applications as system – Now users can interact with an application installation user interface in system context even during a task sequence. This feature is a popular request on UserVoice. This release also includes the following improvement for customers using System Center Configuration Manager connected with Microsoft Intune to manage mobile devices: New options for compliance policies – You can now configure new options for compliance policies for Windows 10 devices. The new settings include policies for Firewall, User Account Control, Windows Defender Antivirus, and OS build versioning. Installing this release So how do you get Technical Preview installed ? There are two methods: Upgrade from a previous installation of Technical Preview (as shown in this guide). Do a clean install of Technical Preview 1703 (the latest TP baseline) by using the following guide and replace the base version in that guide with the TP1703 release and then upgrade. Upgrading to this release Once you have a Technical Preview release installed, in the Configuration Manager console browse to Administration, Overview, Updates and Servicing as shown below. Click on Check for Updates (in the ribbon) Next, click on the OK button. After refreshing the console, you can see the update is available. As instructed, if you want more details about what’s happening, you can read the DMPDownloader.log available in <drvletter>:\Program Files\Microsoft Configuration Manager\Logs, you can use CMTrace to do so. And refresh the console by clicking on the Refresh icon in the ribbon, you should see the update pack is downloading, and once it is downloaded the state will change to Ready to Install. Installing the update Right click the update and choose Install update pack. A wizard appears. Click Next. the Features included in the update pack will be listed. Select your client update settings and click Next accept the EULA and configure the software assurance expiration date and click through to the completion Monitoring the Upgrade At this point you should monitor the CMUpdate.log available in <drvletter>:\Program Files\Microsoft Configuration Manager\Logs, you can use CMTrace to do so. This log will detail the installation of the update pack. You should also pay attention to the following log files present in the root of C:\. CompMgrProv.Log ConfigMgrPrereq.log ConfigMgrSetup.log and after refreshing the console, the state of the update pack will change to Installing. Clicking on Show Status will give you detailed info about the state the Installation is in, it is broken down into 5 distinct phases in the top pane: Download Replication Prerequisite Check Installation Post Installation Selecting a phase will highlight what state the update is in, including what (if any) problems it has. And after a while it should progress through to the Post Installation phase, And after refreshing the console you’ll be informed that a new version is available namely version 5.00.8582.1000. and after a while the new console is installed. After Installing this version, you can check your Upgrade history by navigating to the Updates and Servicing node, and clicking on History in the ribbon. Related reading https://docs.microsoft.com/en-us/sccm/core/get-started/capabilities-in-technical-preview-1711 https://cloudblogs.microsoft.com/enterprisemobility/2017/11/17/update-1711-for-configuration-manager-technical-preview-branch-available-now/
  5. Hi All, Since yesterday i can't open SCCM console (from remote machine and from the main server) I'm getting the default screen when the console will not open (Attached) I accidentally changed permissions under the :"SMS_Site Code" Share and i think this is what caused this problem but I'm not sure. Here is the main error i'm getting from SMSAdmin.log file: 1st error : System.Management.ManagementException\r\nProvider load failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) 2nd Error: Transport error; failed to connect, message: 'The SMS Provider reported an error.'\r\nMicrosoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe SMS Provider reported an error.\r\n at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext() 3rd Erorr: Transport error; failed to connect, message: 'The SMS Provider reported an error.'\r\nMicrosoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe SMS Provider reported an error.\r\n at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext() 4th Error: at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)\r\nConfigMgr Error Object: 5th Error: Error Code: ProviderLoadFailure \r\nSystem.Management.ManagementException\r\nProvider load failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) 6th Erorr: System.Management.ManagementException\r\nProvider load failure \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) Any help will be appreciated! Thank you!!
  6. Hi All, Recently we started experiencing issues with our OSD process creating an "Unknown" computer object with the PC's MAC address as soon as the first "Next" button is clicked at the Welcome to the Task Sequence Wizard screen causing the built to present the "There are not task sequences available for this computer" error. We advertise our task sequences ONLY to the x86/x64 unknown computer objects, so as soon as this object is created in the database the TS availability fails. We are running SCCM 1706 (5.00.8540.1500). Object Properties: Agent Name: "Heartbeat Discovery" Client: NO Client Type: Computer Decommissioned: No MAC Addresses: "A4:4C:C8:0A:C0:2C" Name: Unknown NetBIOS Name: Unknown Resource Type: System Unknown Computer: 1 Attached is the SMSts.log file for review. Any help is greatly appreciated! Matt smsts.log
  7. Hi We are moving from using SCCM OSD to using MDT for Deployments. In our SCCM OSD environment we used an HTA that would take user input and would generate a Computername (Specifically populate the OSDComputerName TS Variable). This worked fine in SCCM but since i've imported this into MDT its not working, meaning the build completes with an MDT generated Name like MININT-87976. I have disabled the computername part in MDT. I have also dumped all the variables during the OS Deployment to a text file, and ive noticed that the OSDComputerName is set to the HTA generated(correct ) name. So it seems like the variable is correct but its not passed to the OS. Any help appreciated and will provide more info if requested. Thanks
  8. Hello, I`m trying to recreate my customsettings.ini file in order to Join and provide a computer name during OSD, i`m wondering if it`s possible to achieve it based on the "constraints" that we have : 1-Diffrent OUs for each type of computer and locations: Desktop and Laptop 2-Diffrent defaultgateway for floor in each location. 3-Diffrent naming convention for each location and diffrent computer type. Thanks,
  9. Gents, I would like to know if it is possible to create a new DP and put the content library on a network share ... From my point of view it should work if we map the network share as a drive, but I cannot find the info on the Internet and I also would like to know if this setup would be supported. The shared folder's physical location would be on a NAS. BR, Sypa
  10. Hello, I have the following failure. We install the SCCM-Client as Pushinstallation/manual installation, some of the installations works, but the most of them just crashs without a real error code. While we install we get the following "red" messages in the ccmsetup.log: After that the installation starts (GET 'HTTP://sccm-01.domain.com/CCM_Client/ccmsetup.cab' ccmsetup 20.10.2017 09:38:44 2164 (0x0874)) MSI: Aktion 09:39:15: GenerateScript. Skriptoperationen werden generiert für Aktion: ccmsetup 20.10.2017 09:39:15 2164 (0x0874) MSI: Aktion 09:39:15: SmsGenerateSuccessMIF. ccmsetup 20.10.2017 09:39:15 2164 (0x0874) Last information of the ccmsetup.log -> <ClientDeploymentMessage ErrorCode="0"><Client Baseline="1" BaselineCookie="" Platform="2" Langs="LP1031"/><Packages><Package ID="{22D00A83-1685-43CF-A3E2-C3E38C3F8CF1}"/></Packages><Additional><SourceType Value="MP"/><SourceLocation Value="HTTP://sccm-01.domain.com/CCM_Client"/><DeploymentMethod Value="1"/></Additional></ClientDeploymentMessage> ccmsetup 20.10.2017 09:40:26 2164 (0x0874) Raised pending client deployment state message. ccmsetup 20.10.2017 09:40:26 2164 (0x0874) Successfully deleted the ccmsetup service ccmsetup 20.10.2017 09:40:31 2164 (0x0874) Deleted file C:\WINDOWS\ccmsetup\ccmsetup.xml ccmsetup 20.10.2017 09:40:31 2000 (0x07D0) Task 'Configuration Manager Client Upgrade Task' does not exist ccmsetup 20.10.2017 09:40:31 2000 (0x07D0) CcmSetup is exiting with return code 0 ccmsetup 20.10.2017 09:40:31 2000 (0x07D0) The Quoted part are the red messages. We extended our AD-Schema, the Boundarie is set, the FallBackBoundarie is set to sccm-01.domain.com. The Client doesnt creat a shortcut under start, when I start the Configuration Manager under controll, I see a deactivated "CCM-Notifaction-Agent", the other components are installed. I hope someone got a good advice for me.. Greets, Mishuri *Edit: I probably find the error/a log entry. In ClientIDManagerStartup i get the following error: To test if the firewall is blocking something, we opened the traffic between our clients and the sccm on any Ports. (Failure/Error still up:( )
  11. I'm close to transitioning over our organization to having SCCM manage software updates. I hope someone could say what are the proper "Windows Update" policies that should be set or modified for SCCM software updates to function correctly. Looking for the recommend settings for the new semi-annual release for Windows 10 servicing. Still have some remaining Windows 7 PCs on network. Thanks!
  12. SCUP and SCCM Windows Update Error 0x8024000f

    Afternoon all, Long time reader but first time posting on the forum. We have SCCM deploying updates via WSUS and SCUP for updating Dell drivers, Adobe etc. On all client machines I'm receiving the following error message when running Windows Update: "There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x8024000f)" My colleague who has since left the company had a similar issue which he described the fix in the following blog post: http://gsilt.blogspot.co.uk/2014/09/scup-wsus-dell-and-error-0x8024000f.html. I've followed this through however I believe with Windows 10 this has now changed slightly as I can no longer find the keywords mentioned in the blog regarding find the references for "cycle" and "DetectUpdates" in the WindowsUpdate.log. All Windows 8.1 and Windows 10 clients are effected by this issue. I have attatched a log file from a Windows 10 machine and also one from Windows 7. Can someone point me in the right direction to get this sorted please as I'm about ready to pull my hair out. I've deleted the published updates from SCUP, imported from the latest catalog and re-published the updates and still no joy.WindowsUpdate.log Any help would be much appreciated. Thanks, C Windows10Update.log
  13. I have an urgent need to image 20 new sites at a new facility we have brought onboard. I set up the new DP and distributed all needed packages. Now when trying to image my task sequence keeps getting stuck at "use Toolkit package step. Ive checked network account settings, and Redeployed "MDT 2013 file" package which is whats under that task but still cant get it to work. Please let me know what else may need to be done on my end.
  14. 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
  15. Hi all, So I had a working boot media. It would boot into the password screen where the network options would be visible. It would then pass through to the task sequence and complete the build as normal. However, upon updating the Distribution Points and creating a final boot media I no longer see the network options. Upon entering the password, the PC just reboots. Worth noting that if I use the boot media created prior to updating all the DP's, it all works (for now the IT Dept are using these). I just can't create new boot media should I need to, in this case was for a background change. I've tried the following: - recreating boot image - recreating boot media - updating MDT Settings and Files - Re-booting SCCM Server - I've been through all the settings and can't see that anything has been changed. Any ideas how to resolve this? Thanks..
  16. Hi I have installed SCCM 1706 on Windows Server 2016 with SQL 2016 running on the same box. When adding and configuring the Software Update Point i have noticed that the 'Products' list has nothing listed post 2010 i.e no Windows 10/Server 2012/2016. I noticed the following prerequisite for Windows 10 servicing: Before you enable the Upgrades classification, you must install WSUS hotfix 3095113 on all software update points in your hierarchy. If you do not install this update, the Windows 10 Servicing feature will not properly function. See http://support.microsoft.com/kb/3095113 for more information. Only Windows Server 2012 and later versions running WSUS support the Upgrade classification of updates. Additionally, to service Windows 10 Version 1607 and later, you must install and configure KB3159706 using the guidance at https://support.microsoft.com/en-us/kb/3159706. WSUS hotfix 3095113 is for Server 2012 and will not install on Server 2016 Any help would be greatly appreciated! Rgds, Simassochelp
  17. Setup: OS: Windows Server 2016 SQL 2016 SCCM Current Branch (1702) Memory: 64GB Disk: 700GB HDD Type: Virtual Machine on a Hyper-V Failover Cluster -------------------------------- I installed ADK v10 then installed SCCM and during the installation process it fails to import the default boot images. Now I have tried to import the boot images but that fails as well, see attachment. There is no AV on this machine as it is a new installation with basic configuration and I have searched this issue but I cannot get an answer for current branch. Could anyone have suggestions to help me out here? I even made sure my account had full permissions on the parent folder down to the file level and I still get the same error. Thank you! ERROR: INFO: Adding Boot Image Packages, this may take some time... Configuration Manager Setup 8/15/2017 2:07:53 PM 6432 (0x1920) INFO: Attempting to export x86 boot image from ADK installation source Configuration Manager Setup 8/15/2017 2:07:53 PM 6432 (0x1920) ERROR: Failed to call method ExportDefaultBootImage. Error 0x80041001 Configuration Manager Setup 8/15/2017 2:07:54 PM 6432 (0x1920) ERROR: Failed to export x86 default boot image from ADK Configuration Manager Setup 8/15/2017 2:07:54 PM 6432 (0x1920) INFO: Attempting to export x64 boot image from ADK installation source Configuration Manager Setup 8/15/2017 2:07:54 PM 6432 (0x1920) ERROR: Failed to call method ExportDefaultBootImage. Error 0x80041001 Configuration Manager Setup 8/15/2017 2:08:04 PM 6432 (0x1920) ERROR: Failed to export x64 default boot image from ADK Configuration Manager Setup 8/15/2017 2:08:04 PM 6432 (0x1920) WARN: Setup does not upgrade customized boot image package. Please update it manually. Configuration Manager Setup 8/15/2017 2:08:04 PM 6432 (0x1920)
  18. Hello, One of my Management Points in SCCM 2012 seems to have developed an issue where it will not allow clients to download Windows updates in software centre. When you click install they just stay on 'waiting to download' and then eventually fail with 'The software change returned error code 0x80240438(-2145123272).' Please can somebody help with this issue and point me in the right direction? Thanks
  19. Trying to install the remote console on a few computers of users that have rights for Remote desktop and operating system deployment. When ever I go and try to open the console on that user's computer it gets the message about not being able to connect to sccm server. I have no problem launching the console on my machine. Any Ideas why this is happening.
  20. I've spent the better part of a day trying to add Adobe reader to our Software Center for users to install. I extracted the MSI files from the executable. I used their Customization app to create the .MST. I've tried setting the install up multiple different ways with no luck. The majority of the time it results in the install in Software Center spinning until it times out. Or it will begin the install correctly, except it's not paying attention to the settings I made in the MST file, and when it finishes, Software Center gives an error that when Googled equates to Software Center being unable to detect that it was installed. Someone out there has to have this working and can throw me a bone.
  21. Is it possible to have a task sequence that skips the client install sccm 2012 R2? The client install package takes very long to deploy none of the hotfixes help the issue. I would just like to put it in the base image and skip that step. is there anyway to put in a step that exits winpe and continues on without that step?
  22. We have a scenario in our organisation where we want to map a huge lot of environment variables for specific machines. Each and every variables are unique to each machine. There are around 6000 variables which needs to be mapped to 6000 machines. Is there any way we can handle it through SCCM ?
  23. Hello WN community! I have a bit of stumper I was hoping to get some feedback on! Let me know what you think... Scenario: We're running SCCM 2012 now for a little over a year, problem free. We've noticed however, that randomly (about 10 out of 1000 clients) the SCCM Client is reporting that the PKI certificate is none. What's stranger still, is that in the ClientIDManagerStartup.log, it doesn't appear to have an issue detecting and selecting the PKI certificate... Directly after the client selects the Cert, the ClientIDManagerStartup.log fills up with this repeating for ages I have ran a repair on the client, same result. I checked to see if perhaps the clients were stuck in provisioning mode, and they're not. Sort of at a loss of what to check next! Any help would be greatly appreciated. Thanks
  24. I am attempting to image a VM by PXE through VSphere. I can successfully PXE boot, but during the "loading files: boot.sdi" it is extremely slow. Then when it attempts to load the WIM, it just sits there. Any thoughts?
  25. Hello all, I've been using SCCM OSD to image machines for about 2 years. Suddenly last month, it stopped working. I assumed that we had a corrupted driver or boot wim. I re-created both the x64 and x86 boot wims, downloaded the newest WinPE 10 drivers, etc. and am still having the issue. When doing PXE boot, I"m getting the failure at preparing network connections. When loading PE from a usb, it loads but then says "There are no task sequences available for this computer." If I do an F8 , ipconfig shows an IP and diskpart shows the drives, which I assume means that I have the correct drivers. Fwiw- I've tried just about every driver combination that I can think of, to no avail. To make matters worse, our MS premier support contract ended the day before it broke and we're waiting for our legal dept. to sign the new enterprise agreement, so I have no MS support. I'm including the smsts.log from one of the machines and wireshark packet traces from a mirrored port for both PXE and USB PE boots. Any assistance is greatly appreciated, as I need to start pushing Win10 out by the end of the month. SCCMPXE-WINPE-Fail-1.pcapng SCCMUSB-WINPE-Fail-1.pcapng smsts-z230.log
×