Jump to content


Search the Community

Showing results for tags 'Sccm'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • 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

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests

  1. All, It has been maybe 3 years since I have touched SCCM but I am getting back in the game! I am going through the process of setting up an SCCM environment for my company and I cannot seem to find the documentation I need. I need help setting up WSUS on a separate server and all of my searches come up with SCCM 2012. Figured it has been 8 years since then and I have to believe this changed a little since then? When I attempted to do this, my SCCM server could not contact my wsus:8530 or wsus:8531 server. I believed I fubar'd this implementation so I am starting all over from scratch again. If anyone could provide me with some guidance, that would greatly be appreciated. I followed the following guides: https://sccmentor.com/2014/09/06/installing-a-remote-software-update-point-on-sccm-2012-r2/ https://sccmentor.com/2014/09/11/installing-a-remote-sup-in-sccm-2012-r2-on-windows-server-2012-r2/
  2. This multi-part guide will show you how to install the latest baseline version of Configuration Manager from Microsoft. The latest available baseline version is System Center Configuration Manager (Current Branch) version 1802 as of March 29th 2018. How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 – Part 1 How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 – Part 2 How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 – Part 3 How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 – Part 4 You can use this multi-part guide to get a hierarchy up and running on Windows Server 2016 using SQL Server 2017. The concept behind this is to guide you through all the steps necessary to get a working Configuration Manager Primary site installed using manual methods or automating it by using PowerShell. This gives you the power to automate the bits that you want to automate, while allowing you to manually do other tasks when needed. You decide which path to take. PowerShell knowledge is desired and dare I say required if you are in any way serious about Configuration Manager. I will show you how to do most steps via two methods shown below, it’s up to you to choose which method suits you best but I highly recommend automating everything that you can (if possible), using PowerShell. Method #1 – Do it manually Method #2 – Automate it with PowerShell In Part 1, you configured Active Directory Domain Services (ADDS) on AD01, then joined the Configuration Manager primary server (CM01) to the newly created domain. You then created users, usergroups and OU's in Active Directory and created the System Management Container. Finally you delegated permission to the Configuration Manager server to the System Management container. In Part 2, you configured Windows Server 2016 roles and features on the Configuration Manager primary server (CM01) and then you downloaded and installed Windows ADK 1709. Next you installed SQL Server 2017 CU5 with SQL Server Management Studio (SSMS) and Reporting Services before installing the WSUS role which uses SQL to store the SUSDB instead of the Windows Internal Database (WID). In this Part, you will download and extract the ConfigMgr content, you'll download the ConfigMgr prerequisites and then you'll extend the Active Directory schema before installing System Center Configuration Manager (Current Branch) version 1802. Step 1. Download and extract the ConfigMgr content Before installing System Center Configuration Manager version 1802 you'll need to download the content as it is a baseline version. You can download baseline versions of the ConfigMgr media from Microsoft's Volume licensing Service Center (VLSC) site for use in production or from MSDN (or the Microsoft Evaluation site) for use in a lab. The VLSC download can be found be searching for Config and then selecting System Center Config Mgr (current branch and LTSB) as shown below. Once you've downloaded the ISO, mount it using Windows File Explorer and copy the contents to somewhere useful like C:\Source\SCCM1802 on the Configuration Manager server. Step 2. Download the ConfigMgr Prerequisites Note: Perform the following on the Configuration Manager server (CM01) as a Local Administrator You can download the prerequisites during ConfigMgr setup or in advance. As you'll probably want to install more than one copy of ConfigMgr (one lab, one production) it's nice to have the prerequisites downloaded in advance. Method #1 – Do it manually To do that, open an administrative PowerShell command prompt and navigate to the following folder: C:\Source\SCCM1802\smssetup\bin\X64 Run the following line .\SetupDL.exe C:\Source\SCCM_Prerequisites Once the process is complete you can open C:\ConfigMgrSetup.log with CMTrace (or notepad) to verify the status of the download. Note: You can find the CMTrace executable in the SMSSetup Tools folder in the location that you extracted the ConfigMgr media, eg: C:\Source\SCCM1802\SMSSETUP\TOOLS. Method #2 – Automate it with PowerShell To automate the download of the prerequisites simply follow the instructions and run the Install SCCM Current Branch version 1802.ps1 Powershell script in Step 4 or use the Download SCCM prerequisite files.ps1. Step 3. Extend the Schema Note: Perform the following on the Domain controller server (AD01) as Administrator. You do not have to extend the Active Directory schema if it was already extended for Configuration Manager previously. Method #1 – Do it manually To do that, on the Active Directory domain controller (AD01), open Windows File Explorer and browse to the network path of the ConfigMgr server where you've copied the SCCM source, eg: \\cm01\c$\Source\SCCM1802\SMSSETUP\BIN\X64 In that folder, locate extadsch.exe and right click, choose Run as Administrator. After the schema has been extended for SCCM, you can open C:\ExtAdsch.log on the root of C:\ on the server you are performing this on, and review the success or failure of that action. Method #2 – Automate it with PowerShell To automate extending the schema, use the Extend the Schema in AD.ps1 PowerShell script. Run the script on the CM01 server using credentials that have the ability to extend the schema. Step 4. Install SCCM Current Branch (version 1802) Note: Perform the following on the ConfigMgr server (CM01) as Administrator. Method #1 – Do it manually To do that, on the Configuration Manager server (CM01), open Windows File Explorer and browse to the network path of the ConfigMgr server where you've copied the SCCM source, eg: C:\Source\SCCM1802\ In that folder, double click on splash.hta. The Installer appears, click on Install. At the Before You Begin screen click Next. In the Available Setup Options screen, place a checkbox in "Use typical Installation options for a stand alone primary site" When prompted if you want to continue click Yes. On the Product Key screen enter your Key (or choose the eval option), and set the Software Assurance Date (optional) On the Product License Terms screen, select the 3 available options and click Next. On the Prerequisite Downloads screen, select the first option and specify C:\Source\SCCM_Prerequisites as the folder to download the prerequisite files. Click Next to start the download. On the Site and Installation Settings screen, enter your chosen site code (eg: P01), your site name and the path where you want to install ConfigMgr. On the Diagnostics and Usage data screen, click Next. On the Service Connection Point Setup screen, enter your choices and click Next. On the Settings Summary, review your choices and when happy with them click Next. On the Prerequisite Check screen click Begin Install when ready. During the installation, click on View Log (opens C:\ConfigmgrSetup.log) to review the installation progress using CMTrace and when the installation is done, click Close. Method #2 – Automate it with PowerShell To automate the installation of ConfigMgr 1802 (including all the previous steps above), simply run the Install SCCM Current Branch version 1802.ps1 PowerShell script. Run the script on the CM01 server and when prompted to extend the schema, enter your choice (yes or no) and if you choose to extend the schema, provide suitable credentials when prompted. Once done with the schema extension, the installation will continue (as shown below). and once installed you can launch the console. Success ! Summary In this 3 part guide you used quite a bit of PowerShell to automate pretty much most of Installing System Center Configuration Manager Current Branch (version 1802), including installing and configuring SQL Server 2017 on Windows Server 2016. Doing it with PowerShell means you can safely say that you've got a handle on Automation using PowerShell. I hope you learned a lot from doing it this way, and until next time, adios ! Downloads The scripts used in this guide are available for download here. Unzip to C:\Scripts on both servers. The scripts are placed in the corresponding folder (Part 1, Part 2 etc) and sorted into which server you should run the script on (AD01 or CM01). Scripts.zip
  3. Microsoft SCCM is an exemplary tool for managing Microsoft applications. But handling third-party applications isn't yet its game. Join our free webinar with Anoop C. Nair, Microsoft MVP, to learn why patching third-party applications is essential and how it can be streamlined in SCCM. Please register here: https://www.manageengine.com/third-party-patching-webinar-with-MVP-Anoop
  4. Anyone tried to determine hardware UEFI capability with SCCM? I am trying to find out if a machine is UEFI capable, cant fine any way to do it at this point.
  5. I am attempting to create and deploy a single universal OSD task sequence in SCCM (current branch) in my organization and will install and apply the appropriate language(and other regional settings) for the region. I have created the task sequence with steps outlined in the thread below. However, Windows 10 version 1903 no longer use standard lp.cab files but rather use the Features on Demand and appx packages to apply languages. There doesnt appear to be any current documentation on how to accomplish this during OSD using sccm with the change in how Windows applies languages. Any assistance would be greatly appreciated. Ive attempted to tackle this problem from a few different angles with no luck. I have also tried the steps outlined below to apply the language/regional settings with similar results. https://thesleepyadmins.com/2019/01/26/sccm-task-sequence-windows-10-language-pack/ In addition to this, I created a bat file package which executes the dism commands to load the .cabs and .appx as well as set the other regional settings to no avail. Running the DISM commands to manually load the 5 different language cab files and the appx (language experience pack) does not actually change the language, or even make it available in the language selection dropdown in Win10 Settings. The only way to get the new language to appear in the dropdown is to go to the MS store and load it on each individual PC even after manually installing the appx. I really want to automate this, and have whatever regional language set as default, and English as the secondary(if applicable). Thanks, Dave
  6. Patch Connect Plus, a third-party add-on for SCCM, brings two new features - Application Management, and Admin Tools to make your SCCM experience comprehensive. Application Management: 1. Select your desired application that needs to be created in SCCM from a vast repository of applications 2. Customize the application deployment with custom scripts and pre-defined application templates Admin Tools: 1. Access 25 of the most essential client management tools from SCCM console 2. Perform a wide range of functions like on-demand client operation, client troubleshooting, and system management actions You can try the fully functional version free for 30 days! Drop a comment should you have any query.
  7. In my Windows 10 LTSC 1809 task sequence, the Install Software Updates step is failing to run. I have attached the log files for the latest attempt to build a test machine. I have deployed the required software update group to both the Unknown Computer collection (as I am deleting the SCCM object for the test machine before each test build) and to a common collection that all of the test machines are put into. The machine does receive and install updates post-build successfully so it is not the software update group or the deployment package as far as I can tell. smsts.zip UpdatesDeployment.log UpdatesHandler.log UpdatesStore.log WUAHandler.log
  8. This multi-part guide will show you how to install the latest baseline version of Configuration Manager from Microsoft. The latest available baseline version is System Center Configuration Manager (Current Branch) version 1802 as of March 29th 2018. How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 – Part 1 How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 – Part 2 How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 – Part 3 How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 – Part 4 You can use this multi-part guide to get a hierarchy up and running on Windows Server 2016 using SQL Server 2017. The concept behind this is to guide you through all the steps necessary to get a working Configuration Manager Primary site installed (for lab use) using manual methods or automated using PowerShell. This gives you the power to automate the bits that you want to automate, while allowing you to manually do other tasks when needed. You decide which path to take. PowerShell knowledge is desired and dare I say required if you are in any way serious about Configuration Manager. I will show you how to do most steps via two methods shown below, it’s up to you to choose which method suits you best but I highly recommend automating everything that you can, using PowerShell. Method #1 – Do it manually Method #2 – Automate it with PowerShell In Part 1, you configured Active Directory Domain Services (ADDS) on AD01, then joined the Configuration Manager server (CM01) to the newly created domain. You then created users, usergroups and OU's in Active Directory and created the System Management Container. Finally you delegated permission to the Configuration Manager server to the System Management container. Step 1. Install Roles and Features on CM01 Note: Perform the following on the Configuration Manager server (CM01) as a Local Administrator To support various features in System Center Configuration Manager, the setup wizard requires some server roles and features preinstalled. On CM01, login as the username you added to the Local Administrators group and start Server Manager. Method #1 - Do it manually The role and feature requirements for ConfigMgr are listed here https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/site-and-site-system-prerequisites. On CM01, login as a user with administrative permissions on the server. Start Server Manager. Click on Add roles and features, on the Before you begin page click Next Choose Role-based or feature-based installation In the Server Selection screen verify CM01.windowsnoob.lab.local is selected and click Next On the Server Roles screen select Web Service (IIS) and when prompted to add features for Web Server (IIS) click on Add Features Click Next and on the Features screen select the .NET Framework 3.5 (includes .NET 2.0 and 3.0) feature Expand the .NET Framework 4.6 Features and select HTTP Activation under WCF Services, answer Add Features when prompted. Select Message Queuing (MSMQ) Activation and when prompted select Add Features Select Named Pipe Activation and TCP Activation and under Background Intelligent Transfer Service (BITS) select IIS Server Extension when prompted to add features click on Add Features Scroll down and select Remote Differential Compression Click Next and on the Web Server Role (IIS) screen click Next on the Select Role Services verify that the following are selected Click Next and point to the Installation Source by clicking on Specify an alternate source path Enter the path to the media eg: E:\Sources\SxS Click Install when ready, at this point you could export configuration settings for later automation Click on Close when the feature installation has succeeded. Method #2 - Automate it with PowerShell Note: Make sure your Server 2016 media is in the drive specified in the script or edit the script to point to the new location of the media. To install the roles and features needed, start Windows Powershell ISE as a user with administrative permissions on the server, edit the variables as appropriate and run the install roles and features.ps1 script. The script will automatically stop and prompt you to correct things, if it cannot find the XML file or the Windows Server 2016 installation media. 1. Extract the scripts to C:\Scripts on CM01 and load the install roles and features.ps1script located in C:\Scripts\Part 2\CM01 2. Edit the variables (lines 18-19) as desired before running. 3. Start Windows PowerShell ISE as Administrator and run the script by clicking on the green triangle. Step 2. Download and install Windows ADK and install WDS Note: Perform the following on the Configuration Manager server (CM01) as a Local Administrator When you deploy operating systems with Configuration Manager, the Windows ADK is an external dependency that is required. The ConfigMgr prerequisite checker will check for various things, including ADK components such as USMT and Windows Preinstallation Environment (among others), therefore you need to install Windows ADK on your server. System Center Configuration Manager version 1802 supports Windows ADK 1709 as I've explained here. Method #1 - Do it manually Go to this link and download ADK 1709. You'll be prompted to save or run ADKSETUP.EXE, select Run. When prompted for the path, accept the defaults...(or change it to something else if you wish) Select your privacy settings Accept the ADK EULA Make sure to have selected at least the following ADK features Deployment Tools Windows Preinstallation Environment (Windows PE) Imaging and Configuration Designer (ICD) Configuration Designer User State Migration tool (USMT) and click Install to start the download and Installation of the Windows ADK, version 1709. Once the ADK installation is complete, click Close. To install WDS, open Server Manager, select Add roles and features and select the Windows Deployment Services role. When prompted click on Add Features to include management tools. and click through the wizard until completion, close the wizard when done. Method #2 - Automate it with PowerShell To download and then install Windows ADK 10 version 1709 with the components needed for ConfigMgr, start Windows Powershell ISE as Administrator and run the setup ADK and WDS.ps1 script. This script not only downloads and installs ADK 1709, but it installs the Windows Deployment Services role. Tip: If you've already downloaded ADK 1709 and want to save yourself some time, copy the Windows Kits folder and all files/folders within to the source folder (eg: C:\Source\Windows Kits) and the script will skip the download. 1. Extract the scripts to C:\Scripts on CM01 and load the setup ADK and WDS.ps1 script located in C:\Scripts\Part 2\CM01 2. Edit the variable (line 17) as desired before running. 3. Start Windows PowerShell ISE as Administrator and run the script by clicking on the green triangle. Step 3. Install SQL Server 2017 Note: Perform the following on the Configuration Manager server (CM01) as a Local Administrator Method #1 - Do it manually Configure the firewall as described in https://go.microsoft.com/fwlink/?linkid=94001. After configuring the firewall, browse to the drive where the SQL Server 2017 media is, and run setup.exe. The SQL Server Installation Center wizard will appear. Click on Installation and then choose New SQL Server standalone installation or add features to an existing installation. Enter the Product Key or use the evaluation version if that's what you want to use. The product key will be automatically filled in for licensed media downloaded from Microsoft Volume Licensing Service Center. Accept the EULA Make your Microsoft Update choices and review your Install rules, select the SQL server instance features you need and if necessary change the drive letter where you intend to install it And configure the Instance Configuration or just leave it as default Verify the Service Accounts settings and for Collation, make sure the collation is set to SQL_Latin1_General_CP1_CI_AS For Server Configuration, click on Add Current User After configuring Data Directories, TempDB and Filestream settings you are Ready to Install Click on Install to start the installation of SQL Server 2017, and once it's completed, click Close. After installing SQL Server 2017, download SQL Server 2017 SSMS from here and install it. Method #2 - Automate it with PowerShell Note: Make sure your SQL Server 2017 media is in the drive specified in the script or edit the script to point to the new location of the media. The script and accompanying INI file have the path pointing at D:\Program Files, please change the variables as appropriate. To install SQL Server 2017 use the Install SQL Server 2017.ps1 script. The script will create a ConfigurationFile.ini used to automate the installation of SQL Server 2017, and after it's installed the script will download the SSMS executable (Management Studio) and install it. Then it will download Reporting Services and install it. If either of the EXE's are in the download folder, it will skip the download and just install. SQL Server no longer comes with the Management Studio or Reporting Services built in, and they are offered as separate downloads, don't worry though, my PowerShell script takes care of that for you. 1. Extract the scripts to C:\Scripts on CM01 and load the Install SQL Server 2017.ps1 script located in C:\Scripts\Part 2\CM01 2. Edit the variables [lines 17-76] as desired before running. 3. Start Windows PowerShell ISE as Administrator and run the script by clicking on the green triangle. Step 4. Restart the Configuration Manager Primary Server Note: Perform the following on the Configuration Manager server (CM01) as a Local Administrator Open an administrative command prompt and issue the following command: shutdown /r Step 5. Install the WSUS role Note: Perform the following on the Configuration Manager server (CM01) as a Local Administrator Now that SQL server is installed, we can utilize SQL Server for the WSUS database. To install WSUS and configure it to use the SQL server database instead of the Windows Internal Database, do as follows: Method #1 - Do it manually Using Roles and Features in Server Manager, add the Windows Server Update Services role. When prompted to add features for the WSUS role, click on Add features. When prompted for the Role Services, uncheck WID Connectivity and add SQL Server Connectivity instead. When prompted for Content location, enter a valid path When prompted for Database Instance Selection, enter the server name and click on Check Connection On the Confirm Installation Selections screen, click on Install. and finally click close. After installing the WSUS role, in Server Manager, click on the yellow exclamation mark and choose Launch Post Installation Tasks. When the tasks are completed Optional: The WSUS database (SUSDB) can be observed using SQL Server SSMS. Method #2 - Automate it with PowerShell Browse to the location where you extracted the scripts, C:\scripts. Start Windows PowerShell ISE as administrator, open the Install roles and features_WSUS.ps1 script, edit the $servername variable and replace CM01 with the ServerName your are installing ConfigMgr on (SQL server). Note: Make sure to have your Windows Server 2016 media in the path referred to by $Sourcefiles. 1. Extract the scripts to C:\Scripts on CM01 and load the Install roles and features_WSUS.ps1 script located in C:\Scripts\Part 2\CM01 2. Edit the variables [lines 22-25] as desired before running. 3. Start Windows PowerShell ISE as Administrator and run the script by clicking on the green triangle. Downloads The scripts used in this guide are available for download here. Unzip to C:\Scripts on both servers. The scripts are placed in the corresponding folder (Part 1, Part 2 etc) and sorted into which server you should run the script on (AD01 or CM01). Scripts.zip Summary Using PowerShell to automate things leaves more time for yourself and it's fun. Please join me in Part 3 of this multi-part guide when you will install System Center Configuration Manager version 1802 (Current Branch).
  9. Hello, I am trying to put together a SCCM standalone OSD build media which is based on our production Windows 10 TS. The production TS wipes the disk (existing Windows 7) and installs Win 10. The solution now works end to end as expected on a virtual machine however when it comes to a physical machine, I am running into a strange behaviour where in after configuring the HP BIOS (secure boot etc.) in WinPE, during the subsequent reboot, instead of booting into the staged Winpe from the HDD to continue with the TS, it once again boots from the Standalone media USB and starts the build process all over again. The overall steps of my Standalone TS are as below: 1. Trigger the autorun TS exe from the running Windows 7 OS USB drive 2. Enter the password to start the TS 3. Select the only standalone TS presented 4. Disable bitlocker 5. Reboot (to boot image assigned to this TS) 6. Convert BIOS to UEFI (if it is not already UEFI) 7. Restart computer (to boot image assigned to this TS) 8. Partition disk 9. Configure HP BIOS **** This is where it configures secure boot, bios password etc. Everything seems to be working as expected up until this stage I have attached the smsts.log as well as the HP Bios utility output captured at this stage 10. Reboot (to boot image assigned to this TS) This is the stage where it starts all over again booting into the inserted USB and starts the standalone task sequence by prompting for the media password (of step 2 above). Just wanted to know what I am doing wrong. Why is the TS starting all over again booting into the USB? I highly suspect, at the BIOS configuration stage, something happens at the BIOS level because of which, during the subsequent reboot, the HDD is not “visible” to the boot manager and hence falls back to the next boot order option which is the USB containing the standalone boot media. When I remove the USB, the boot fails with DOS-style prompt (with black background) with the message ">>Start PXE over IPv4". If I continue to boot into USB, and F8 and check the disk, there is C drive with bootmgt,bootmgr.efi files as well as sms flder, Sources folder (with boot.wim), _SMSTaskSequence folder etc. I can even run diskpart. With Disk 0 selected, I can see 4 partitions (system, Reserved,Primary,Recovery) Any thoughts? Is there anything that I can do in terms of the troubleshooting to know what’s happening? Thank you. smsts.log HP Bios Utility Output.txt
  10. I have an issue with 2 client PCs software center not working since past 2 days. The is Operating System task sequence targeted to these PCs to make it as a Master PC to stage other Windows clients.The task sequence have 1809 configurations. When I open Software Center-> OS tab -> Click Win10 1809 configuration task sequence -> Install -> The TS does not run and show above error.I have checked boundaries and Boundary groups of this region and they are pointing to nearest Distribution Point (DP) and the site code is added to correct Boundary Group.I uninstall and re-install ccm on both PCs but same issue. Tried installing CCM with below switchCCMSetup.exe /mp:SMSMP01 /logon SMSSITECODE=C01LocationService.log:-Unable to retrieve AD site membership LocationServices 8/8/2019 12:30:59 AM 8408 (0x20D8)Unable to retrieve AD site membership LocationServices 8/8/2019 12:30:59 AM 8408 (0x20D8)Client is not in any boundary group and ConfigMgr is no longer managing WindowsDO GPO. Set WindowsDO GPO to default values. Mode = LAN. GroupID = empty LocationServices 8/8/2019 12:30:59 AM 8408 (0x20D8)The number of discovered DPs(including Branch DP and Multicast) is 0 LocationServices 8/8/2019 12:30:59 AM 8408 (0x20D8)CAS.log:-Location update from CTM for content Content_ccb6ec31-7759-4a0f-b511-bff5e786ec41.1 and request {43EA474D-0182-4D6E-B2E9-35C7B3F65B9D} ContentAccess 8/8/2019 12:26:12 AM 3276 (0x0CCC)Download request only, ignoring location update ContentAccess 8/8/2019 12:26:12 AM 3276 (0x0CCC)My site server configuration:-DPs- USDP01.abc.abc.comBoundary:- USPC- Type: AD site- SiteSystem: USDP01.abc.abc.comBoundary Group:- PS2Boundary (Primary Server name)- USDP01.abc.abc.comPC's are in PS2:-USPC01 USPC02Any ideas how to fix this?
  11. Hello. I have such xml file <?xml version="1.0" encoding="UTF-8"?> <migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/IncludeExtensionsandExcludeFixedDisc"> <_locDefinition> <_locDefault _loc="locNone"></_locDefault> <_locTag _loc="locData">displayName</_locTag> </_locDefinition> <!-- This component migrates user files with known extensions--> <component type="Documents" context="System"> <displayName _locID="miguser.userdata">Scan for user data in system root</displayName> <role role="Data"> <rules> <include> <objectSet> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.323]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.3gp]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.aa]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.aac]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.accdb]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.acd]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.acsup]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.adb]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.ade]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.adn]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.adp]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.ai]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.aif]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.aiff]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.arc]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.asf]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.asx]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.avi]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.avsup]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.avs]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.bhx]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.bjx]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.bmp]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.box]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.bqy]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.btw]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.cad]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.cda]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.cer]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.chf]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.CLASS]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.cnf]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.cpp]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.CSS]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.CT]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.cvsup]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.cxx]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.c]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.db*]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.DGC]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.dic]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.dsk]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.dsp]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.dwf]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.dwg]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.dxf]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.epf]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.eps]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.fav]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.fdf]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.FH10]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.FH7]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.FH8]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.fm]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.fpc]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.fphtml]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.gho]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.ghs]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.gif]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.GRS]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.gz]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.hmx]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.hpp]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.hqx]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.html]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.htm]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.hxx]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.h]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.idx]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.id]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.iff]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.ifo]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.iii]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.img]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.inl]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.iso]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.jpeg]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.jpg]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.JS]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.lic]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.m3u]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.m4a]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.m4p]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.m4v]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mak]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mbx]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.md1]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mda]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mde]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mdl]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mdw]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.midi]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mid]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mkv]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mod]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.moov]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.movie]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mov]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mp1]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mp2]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mp3]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mp4]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mpa]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mpd]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mpeg]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mpe]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mpg]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mpj]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mpt]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mpw]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mpx]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.msg]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mus]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.nk2]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.NRG]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.nsf]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.nsk]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.oce]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.odb]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.oft]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.opx]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.ora]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.ost]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.p12]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.pab]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.PAF]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.pdf]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.pfx]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.PHP]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.pjx]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.pm3]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.pm4]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.pm5]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.pm6]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.pm7]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.png]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.pot*]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.potm]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.potx]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.ppam]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.pqi]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.prf]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.prn]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.pro]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.ps]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.pwz]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.qpr]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.qtm]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.qt]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.qvw]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.ram]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.rar]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.ra]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.rbs]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.rm]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.rql]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.rsf]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.rvx]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.rxc]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.scm]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.scx]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.snp]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.spd]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.spk]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.sql]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.swf]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.tab]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.tar]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.taz]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.tif]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.tgz]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.tml]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.TRC]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.tz]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.uls]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.uu]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.vbg]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.vcd]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.vcx]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.vhd]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.vmc]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.vmdk]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.vmv]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.vmx]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.vob]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.vpb]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.vss]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.vst]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.vsw]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.vue]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.wav]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.wma]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.wmv]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.xcl]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.zip]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.qdf]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.qsd]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.qel]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.qph]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.doc*]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.dot*]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.rtf]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mcw]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.wps]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.scd]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.wri]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.wpd]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.xl*]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.csv]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.iqy]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.dqy]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.oqy]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.rqy]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.wk*]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.wq1]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.slk]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.dif]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.ppt*]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.pps*]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.pot*]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.sh3]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.ch3]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.pre]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.ppa]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.txt]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.pst]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.one*]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.vl*]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.vsd]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mpp]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.or6]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.accdb]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.mdb]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("* [*.pub]", "Fixed")</script> </objectSet> </include> <exclude> <objectSet> <script>MigXmlHelper.GenerateDrivePatterns ("\Winnt\* [*]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("\Windows\* [*]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("\TEMP\* [*]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("\TEMP1\* [*]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("\TEMP2\* [*]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("\MIGF\* [*]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("\_SMSTaskSequence\* [*]", "Fixed")</script> <pattern type="File">%CSIDL_WINNT%\* [*]</pattern> <pattern type="File">%CSIDL_WINDOWS%\* [*]</pattern> <pattern type="File">%CSIDL_DEFAULT_INTERNET_CACHE%\* [*]</pattern> <pattern type="File">%CSIDL_INTERNET_CACHE%\* [*]</pattern> <pattern type="File">%CSIDL_INTERNET_CACHE%\LOW\* [*]</pattern> <pattern type="File">%TEMP%\* [*]</pattern> <pattern type="File">%CSIDL_PROGRAM_FILES%\* [*]</pattern> <pattern type="File">%CSIDL_PROGRAM_FILESX86%\* [*]</pattern> <!-- <pattern type="File">%SYSTEMDRIVE%\Users\* [*]</pattern> --> <pattern type="File">%SYSTEMDRIVE%\TEMP1\* [*]</pattern> <pattern type="File">%SYSTEMDRIVE%\TEMP2\* [*]</pattern> <pattern type="File">%SYSTEMDRIVE%\_SMSTaskSequence\* [*]</pattern> <pattern type="File">%SYSTEMDRIVE%\UserOld\* [*]</pattern> <pattern type="File">%SYSTEMDRIVE%\UserOld\ [*]</pattern> </objectSet> </exclude> </rules> </role> </component> <!-- UnconditionalExclude SECTION --> <component type="Documents" context="System"> <displayName _locID="miguser.userdata">Common Exclusions</displayName> <role role="Data"> <rules> <unconditionalExclude> <objectSet> <!--We are trying to remove system files from other windows installation on the same machine--> <!-- I've moved the unconditional excludes for the WINDOWS dir to EXCLUDES due to wallpaper requirements --> <pattern type="File">%CSIDL_DEFAULT_INTERNET_CACHE%\* [*]</pattern> <pattern type="File">C:\Users\*\AppData\Local\Microsoft\Windows\Temporary Internet Files\* [*]</pattern> <pattern type="File">%CSIDL_WINDOWS%\Media\* [*]</pattern> <pattern type="File">C:\Drivers\*[*]</pattern> <pattern type="File">C:\MININT\*[*]</pattern> </objectSet> </unconditionalExclude> </rules> </role> </component> <!-- Conditional exclude section --> <component type="Documents" context="System"> <displayName _locID="miguser.userdata">Conditional D Drive Exclusion</displayName> <role role="Data"> <rules> <conditions> <condition>MigXmlHelper.DoesObjectExist("File","D:\User State Migration Tool")</condition> </conditions> <unconditionalExclude> <objectSet> <pattern type="File">D:\* [*]</pattern> </objectSet> </unconditionalExclude> </rules> </role> </component> <component type="Documents" context="System"> <displayName _locID="miguser.userdata">Conditional E Drive Exclusion</displayName> <role role="Data"> <rules> <conditions> <condition>MigXmlHelper.DoesObjectExist("File","E:\User State Migration Tool")</condition> </conditions> <unconditionalExclude> <objectSet> <pattern type="File">E:\* [*]</pattern> </objectSet> </unconditionalExclude> </rules> </role> </component> <component type="Documents" context="System"> <displayName _locID="miguser.userdata">Conditional F Drive Exclusion</displayName> <role role="Data"> <rules> <conditions> <condition>MigXmlHelper.DoesObjectExist("File","F:\User State Migration Tool")</condition> </conditions> <unconditionalExclude> <objectSet> <pattern type="File">F:\* [*]</pattern> </objectSet> </unconditionalExclude> </rules> </role> </component> </migration> Use the /hardlink. After installing Windows 10, I move several folders to the User Old folder. How do I prevent files and folders from being recovered from UserOld?
  12. Can a google chrome extension be added as part of a packaged installer along with the msi
  13. Hi Everyone,

    I'm a new Level 2 Technician as i was previously Level 1 technician and my main role was helping users troubleshoot issues on their Computer and recently had a few colleagues from Level 3 started helping me get into SCCM environment were i flourishing from their Wisdom, so found your site and started to visit this site to learn a few things and decided to register.

    Thank you for visiting my page

  14. I recently upgraded my SCCM environment to 1902, I then did a 1903 Feature update to a laptop which was successful. I made the Products and Classification change in SCCM to make Windows 10 1903 software updates available. I created a deployment packed that included 1903 updates and deploy it to a combination of Windows 7, 10 1803 and 1903 devices. The Windows 7 and 10 1803 devices applied the updates successfully but both of the 1903 devices are giving me a message in software Center that there are "Insufficient Permissions for Software Installation, Your IT department has set restrictions for this software that prevent it from installing on your computer." Has anyone else run into this?
  15. This multi-part guide will show you how to install the latest baseline version of Configuration Manager from Microsoft. The latest available baseline version is System Center Configuration Manager (Current Branch) version 1802 as of March 29th 2018. How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 – Part 1 How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 – Part 2 How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 – Part 3 How can I install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017 – Part 4 You can use this multi-part guide to get a hierarchy up and running on Windows Server 2016 using SQL Server 2017. The concept behind this is to guide you through all the steps necessary to get a working Configuration Manager Primary site installed using manual methods or automating it by using PowerShell. This gives you the power to automate the bits that you want to automate, while allowing you to manually do other tasks when needed. You decide which path to take. PowerShell knowledge is desired and dare I say required if you are in any way serious about Configuration Manager. I will show you how to do most steps via two methods shown below, it’s up to you to choose which method suits you best but I highly recommend automating everything that you can (if possible), using PowerShell. Method #1 – Do it manually Method #2 – Automate it with PowerShell In Part 1, you configured Active Directory Domain Services (ADDS) on AD01, then joined the Configuration Manager primary server (CM01) to the newly created domain. You then created users, usergroups and OU's in Active Directory and created the System Management Container. Finally you delegated permission to the Configuration Manager server to the System Management container. In Part 2, you configured Windows Server 2016 roles and features on the Configuration Manager primary server (CM01) and then you downloaded and installed Windows ADK 1709. Next you installed SQL Server 2017 CU5 with SQL Server Management Studio (SSMS) and Reporting Services before installing the WSUS role which uses SQL to store the SUSDB instead of the Windows Internal Database (WID). In Part 3, you downloaded and extracted the ConfigMgr content, you downloaded the ConfigMgr prerequisites and then you extended the Active Directory schema before installing System Center Configuration Manager (Current Branch) version 1802. In this part you'll create some device collections to prepare your lab for Servicing Windows 10, whether using WAAS or Upgrade Task Sequences built into ConfigMgr. The collections create include some based on the recently released Windows 10 version 1803. Step 1. Create some device collections Note: Perform the following on the Configuration Manager server (CM01) as a Local Administrator You can create collections using the ConfigMgr console and clicking your way through the wizard, you'll need to add membership queries to populate the collections, and include Include or Exclude rules as appropriate. Method #1 – Do it manually <to be added> Method #2 – Automate it with PowerShell To automate the creation of a bunch of device collections simply run the CreateDeviceCollectionsWindows10.ps1 Powershell script by starting PowerShell ISE as Administrator on the ConfigMgr server (CM01). Summary In this guide you created a whole bunch of collections to sort all your Windows 10 computers into easily identifiable groups based on Windows Version number, so that you can target them with policy or use Upgrade task sequences or Windows Servicing. Downloads The scripts used in this guide are available for download here. Unzip to C:\Scripts on both servers. The scripts are placed in the corresponding folder (Part 1, Part 2 etc) and sorted into which server you should run the script on (AD01 or CM01). Scripts.zip
  16. So l’m kind new to SCCM’s OSD and I’ve been assigned to do an upgrade for Windows 7 workstation to Windows 10 v1703. I read online that the maximum ADK supported by SCCM 1606 is v1607, lucky I also read some posts online saying that it worked fine with Windows 10 v1706 although Microsoft does not support it. Now, my questions is our environment has an older ADK version that I don’t wish to remove if that possible. Can I just install the new ADK + upload new images to console + use new USMT Package for user data migration? Or must I upgrade the whole winPE to the new ADK environment? And if so, is there is any easier way then using scripts to update image and adk level ? ( older SCCM versions don’t have the option of reloading boot images) *current environment has two ADKs !! win 8.1 /older version of win 10 adk . If anyone can guide me please, I’m supposed to start the upgrade as soon as possible as windows 7 is going to be out of support in 2020.
  17. 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.
  18. I have been tasked to make a change to a currnt SCCM Env', at present they have Primary site - Severs only are managed here and the server support team mange the whole environment we are looking to add secondary site - this will be used to manage the workstations, a team of EUC sepport will manage the devices, but will have no access to the primary site. The SCCM will soo move to Co-Management the comapny does not want to move to CAS will a primary site do what we want, i have heard that in Co-Management the secondary site cannot be managed from its MP but only from the primary site any advice guys?
  19. Hello. There is the following command @echo off setLocal Enabledelayedexpansion for %%d in (c d e f g h i j k l m n o p q r s t u v w x y z) do ( if exist %%d:\"STORE USER ARM"\ ( xcopy %%d:"\User State Migration Tool\*.*" /e /v /y C:\Windows\USMT\ If not exist %%d:\Store Mkdir %%d:\Store c: cd C:\Windows\USMT\Amd64 scanstate.exe %%d:\Store\%ComputerName% /c /o /ue:%OSDCOMPUTERNAME%\* /hardlink /nocompress /i:MigApp.xml /i:MigCustom.xml /i:MigUser.xml /i:MigProgFiles.xml /v:5 /l:%%d:\Store\%ComputerName%\logs\scanstate.log /progress:%%d:\Store\%ComputerName%\logs\scanstate_progress.log )) The idea is to run the task sequence from a flash drive and save user data on the same flash drive. The script works, but does not work through the sequence. How does one make this option or maybe there is an alternative?
  20. I'm in the process of automating reader so that it downloads and creates the application in SCCM We use a global condition to get the version of reader out of the registry. I have two deployment types, One installs the full reader and the second just installs the patch. On the second deployment type we use the requirement Between operand with the values of "17.011.130000" "17.011.130080" that way it will only install the patch it fails on the between operand. If I use greaterthan or others it works fine. Any help???? Here is the error message. Add-CMScriptDeploymentType : ConfigMgr Error Object: instance of SMS_ExtendedStatus { Description = "There is a failure while generating lantern documents for this configuration item"; ErrorCode = 1078462256; File = "..\\sspconfigurationitem.cpp"; Line = 2164; Operation = "PutInstance"; ParameterInfo = ""; ProviderName = "ExtnProv"; StatusCode = 2147749889; }; At C:\Reader\Add-Depend.ps1:155 char:1 + Add-CMScriptDeploymentType -SourceUpdateProductCode "$ReaderGUID" -A ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (Microsoft.Confi...mentTypeCommand:AddScriptDeploymentTypeCommand) [Add-CMScriptDeploymentType], WqlQueryException + FullyQualifiedErrorId : UnhandledException,Microsoft.ConfigurationManagement.Cmdlets.AppMan.Commands.AddScriptDeploymentTypeCommand
  21. Hi, I thought I would advertise my book here as I need all the shout-outs I can get! The book is entitled: ConfigMgr - An Administrator's Guide to Deploying Applications using PowerShell I think it's pretty good, but then again, I'm probably biased. You can get it here: https://leanpub.com/configmgr-DeployUsingPS Sorry about this advert - I hate adverts too. Sometimes, you just...gotta.
  22. Trying to enable Wake on LAN to a mass amount of already deployed workstations. I pulled down Dell's CCTK. Enabled the Wake on LAN feature for all models and dumped out an EXE from the software. Packaged it in SCCM, and it successfully gets pulled down. However, when SCCM is running the install execmgr.log keeps telling me: Script for Package:CU100103, Program: Dell BIOS Settings Wake On LAN failed with exit code 10 The advertisement status on the console tells me the same information. Has anyone had much experience deploying CCTKs this way? I have included images of the packages program settings; as it might be something in the manor I am telling it to run. Any help is appreciated. Also, Windows Noob is a job saver.
  23. Good morning, I am experiencing an issue with my wireless clients. I'm able to get some information. However, I am unable to get any software deployed to them. For example: - I get the green check, I am getting policy requests, heartbeat DDR, hardware scan, etc. I have the following applications deployed to a collection, I've kicked off "Machine Policy Retrieval & Evaluation Cycle" on the client, and wait. After a bit, I check the ccmcache folder, and all I see is this: " Upon investigating CAS.log, I see the following messages. Location update from CTM for content Content_9fca0c3a-abb4-45cf-8607-9002e09ff55d.1 and request {5BE028BD-31EF-40D7-ACCC-B68B5EAB238A} ContentAccess 3/29/2019 12:29:12 AM 8724 (0x2214) Download request only, ignoring location update ContentAccess 3/29/2019 12:29:12 AM 8724 (0x2214) Location update from CTM for content Content_f71ec7c6-8d83-4cff-baed-d042bee249db.1 and request {D933FF2F-430E-4AA3-9B2C-061131DA6764} ContentAccess 3/29/2019 12:29:13 AM 3416 (0x0D58) Download request only, ignoring location update ContentAccess 3/29/2019 12:29:13 AM 3416 (0x0D58) Location update from CTM for content Content_79793beb-8d31-491e-b97d-6e83188fa407.1 and request {3E6E2FEA-A93F-4642-9B18-B8006B334F95} ContentAccess 3/29/2019 12:29:13 AM 3416 (0x0D58) Download request only, ignoring location update ContentAccess 3/29/2019 12:29:13 AM 3416 (0x0D58) Location update from CTM for content Content_5354c64f-945a-4b08-a003-064130a4566a.1 and request {AEF8926C-5624-4BC0-B24F-1B7D4758212D} ContentAccess 3/29/2019 12:29:13 AM 4256 (0x10A0) Download request only, ignoring location update ContentAccess 3/29/2019 12:29:13 AM 4256 (0x10A0) Location update from CTM for content Content_3bea231e-1c77-4cda-8026-85eebee83451.1 and request {FA24E938-E4C0-4B3D-B0B8-ABD927785070} ContentAccess 3/29/2019 12:29:13 AM 4256 (0x10A0) Download request only, ignoring location update ContentAccess 3/29/2019 12:29:13 AM 4256 (0x10A0) Location update from CTM for content Content_637b724f-2a10-4111-9ca0-b0583587edaa.1 and request {F1AD0338-79E5-43B8-A996-D0E573C57A97} ContentAccess 3/29/2019 12:29:13 AM 7972 (0x1F24) Download request only, ignoring location update ContentAccess 3/29/2019 12:29:13 AM 7972 (0x1F24) Location update from CTM for content LIB00003.15 and request {9E0C4E3D-1981-4E35-8872-22BDDEED324F} ContentAccess 3/29/2019 12:29:13 AM 7972 (0x1F24) Download request only, ignoring location update ContentAccess 3/29/2019 12:29:13 AM 7972 (0x1F24) Location update from CTM for content Content_6a919932-b12f-46e1-be00-73c7d9c33269.1 and request {FF212273-2733-494F-87EE-33D06D76368A} ContentAccess 3/29/2019 12:29:13 AM 3416 (0x0D58) Download request only, ignoring location update ContentAccess 3/29/2019 12:29:13 AM 3416 (0x0D58) Location update from CTM for content Content_f7c36f23-6552-4ba8-b79c-2fb0d0a6463f.1 and request {CAEC8A21-7228-465F-80BC-BE1833D7321C} ContentAccess 3/29/2019 12:29:13 AM 7972 (0x1F24) Download request only, ignoring location update ContentAccess 3/29/2019 12:29:13 AM 7972 (0x1F24) Location update from CTM for content Content_9fca0c3a-abb4-45cf-8607-9002e09ff55d.1 and request {5BE028BD-31EF-40D7-ACCC-B68B5EAB238A} ContentAccess 3/29/2019 1:29:12 AM 3416 (0x0D58) Download request only, ignoring location update ContentAccess 3/29/2019 1:29:12 AM 3416 (0x0D58) Location update from CTM for content Content_f71ec7c6-8d83-4cff-baed-d042bee249db.1 and request {D933FF2F-430E-4AA3-9B2C-061131DA6764} ContentAccess 3/29/2019 1:29:13 AM 3416 (0x0D58) Download request only, ignoring location update ContentAccess 3/29/2019 1:29:13 AM 3416 (0x0D58) Location update from CTM for content Content_79793beb-8d31-491e-b97d-6e83188fa407.1 and request {3E6E2FEA-A93F-4642-9B18-B8006B334F95} ContentAccess 3/29/2019 1:29:13 AM 3416 (0x0D58) Download request only, ignoring location update ContentAccess 3/29/2019 1:29:13 AM 3416 (0x0D58) Location update from CTM for content Content_5354c64f-945a-4b08-a003-064130a4566a.1 and request {AEF8926C-5624-4BC0-B24F-1B7D4758212D} ContentAccess 3/29/2019 1:29:13 AM 2532 (0x09E4) Download request only, ignoring location update ContentAccess 3/29/2019 1:29:13 AM 2532 (0x09E4) Location update from CTM for content Content_3bea231e-1c77-4cda-8026-85eebee83451.1 and request {FA24E938-E4C0-4B3D-B0B8-ABD927785070} ContentAccess 3/29/2019 1:29:13 AM 4372 (0x1114) Download request only, ignoring location update ContentAccess 3/29/2019 1:29:13 AM 4372 (0x1114) Location update from CTM for content Content_637b724f-2a10-4111-9ca0-b0583587edaa.1 and request {F1AD0338-79E5-43B8-A996-D0E573C57A97} ContentAccess 3/29/2019 1:29:13 AM 4372 (0x1114) Download request only, ignoring location update ContentAccess 3/29/2019 1:29:13 AM 4372 (0x1114) Location update from CTM for content LIB00003.15 and request {9E0C4E3D-1981-4E35-8872-22BDDEED324F} ContentAccess 3/29/2019 1:29:13 AM 2532 (0x09E4) Download request only, ignoring location update ContentAccess 3/29/2019 1:29:13 AM 2532 (0x09E4) Location update from CTM for content Content_6a919932-b12f-46e1-be00-73c7d9c33269.1 and request {FF212273-2733-494F-87EE-33D06D76368A} ContentAccess 3/29/2019 1:29:13 AM 3856 (0x0F10) Download request only, ignoring location update ContentAccess 3/29/2019 1:29:13 AM 3856 (0x0F10) Location update from CTM for content Content_f7c36f23-6552-4ba8-b79c-2fb0d0a6463f.1 and request {CAEC8A21-7228-465F-80BC-BE1833D7321C} ContentAccess 3/29/2019 1:29:13 AM 7276 (0x1C6C) Download request only, ignoring location update ContentAccess 3/29/2019 1:29:13 AM 7276 (0x1C6C) Location update from CTM for content Content_9fca0c3a-abb4-45cf-8607-9002e09ff55d.1 and request {5BE028BD-31EF-40D7-ACCC-B68B5EAB238A} ContentAccess 3/29/2019 2:29:13 AM 4620 (0x120C) Download request only, ignoring location update ContentAccess 3/29/2019 2:29:13 AM 4620 (0x120C) Location update from CTM for content Content_f71ec7c6-8d83-4cff-baed-d042bee249db.1 and request {D933FF2F-430E-4AA3-9B2C-061131DA6764} ContentAccess 3/29/2019 2:29:13 AM 4984 (0x1378) Download request only, ignoring location update ContentAccess 3/29/2019 2:29:13 AM 4984 (0x1378) Location update from CTM for content Content_79793beb-8d31-491e-b97d-6e83188fa407.1 and request {3E6E2FEA-A93F-4642-9B18-B8006B334F95} ContentAccess 3/29/2019 2:29:13 AM 6088 (0x17C8) Download request only, ignoring location update ContentAccess 3/29/2019 2:29:13 AM 6088 (0x17C8) Location update from CTM for content Content_5354c64f-945a-4b08-a003-064130a4566a.1 and request {AEF8926C-5624-4BC0-B24F-1B7D4758212D} ContentAccess 3/29/2019 2:29:13 AM 7584 (0x1DA0) Download request only, ignoring location update ContentAccess 3/29/2019 2:29:13 AM 7584 (0x1DA0) Location update from CTM for content Content_3bea231e-1c77-4cda-8026-85eebee83451.1 and request {FA24E938-E4C0-4B3D-B0B8-ABD927785070} ContentAccess 3/29/2019 2:29:13 AM 7276 (0x1C6C) Download request only, ignoring location update ContentAccess 3/29/2019 2:29:13 AM 7276 (0x1C6C) Location update from CTM for content Content_637b724f-2a10-4111-9ca0-b0583587edaa.1 and request {F1AD0338-79E5-43B8-A996-D0E573C57A97} ContentAccess 3/29/2019 2:29:13 AM 7276 (0x1C6C) Download request only, ignoring location update ContentAccess 3/29/2019 2:29:13 AM 7276 (0x1C6C) Location update from CTM for content LIB00003.15 and request {9E0C4E3D-1981-4E35-8872-22BDDEED324F} ContentAccess 3/29/2019 2:29:13 AM 5576 (0x15C8) Download request only, ignoring location update ContentAccess 3/29/2019 2:29:13 AM 5576 (0x15C8) Location update from CTM for content Content_6a919932-b12f-46e1-be00-73c7d9c33269.1 and request {FF212273-2733-494F-87EE-33D06D76368A} ContentAccess 3/29/2019 2:29:14 AM 7584 (0x1DA0) Download request only, ignoring location update ContentAccess 3/29/2019 2:29:14 AM 7584 (0x1DA0) Location update from CTM for content Content_f7c36f23-6552-4ba8-b79c-2fb0d0a6463f.1 and request {CAEC8A21-7228-465F-80BC-BE1833D7321C} ContentAccess 3/29/2019 2:29:14 AM 5576 (0x15C8) Download request only, ignoring location update ContentAccess 3/29/2019 2:29:14 AM 5576 (0x15C8) Location update from CTM for content Content_9fca0c3a-abb4-45cf-8607-9002e09ff55d.1 and request {5BE028BD-31EF-40D7-ACCC-B68B5EAB238A} ContentAccess 3/29/2019 3:29:13 AM 2124 (0x084C) Download request only, ignoring location update ContentAccess 3/29/2019 3:29:13 AM 2124 (0x084C) Location update from CTM for content Content_f71ec7c6-8d83-4cff-baed-d042bee249db.1 and request {D933FF2F-430E-4AA3-9B2C-061131DA6764} ContentAccess 3/29/2019 3:29:13 AM 3856 (0x0F10) Download request only, ignoring location update ContentAccess 3/29/2019 3:29:13 AM 3856 (0x0F10) Location update from CTM for content Content_79793beb-8d31-491e-b97d-6e83188fa407.1 and request {3E6E2FEA-A93F-4642-9B18-B8006B334F95} ContentAccess 3/29/2019 3:29:14 AM 4028 (0x0FBC) Download request only, ignoring location update ContentAccess 3/29/2019 3:29:14 AM 4028 (0x0FBC) Location update from CTM for content Content_5354c64f-945a-4b08-a003-064130a4566a.1 and request {AEF8926C-5624-4BC0-B24F-1B7D4758212D} ContentAccess 3/29/2019 3:29:14 AM 3856 (0x0F10) Download request only, ignoring location update ContentAccess 3/29/2019 3:29:14 AM 3856 (0x0F10) Location update from CTM for content Content_3bea231e-1c77-4cda-8026-85eebee83451.1 and request {FA24E938-E4C0-4B3D-B0B8-ABD927785070} ContentAccess 3/29/2019 3:29:14 AM 7276 (0x1C6C) Download request only, ignoring location update ContentAccess 3/29/2019 3:29:14 AM 7276 (0x1C6C) Location update from CTM for content Content_637b724f-2a10-4111-9ca0-b0583587edaa.1 and request {F1AD0338-79E5-43B8-A996-D0E573C57A97} ContentAccess 3/29/2019 3:29:14 AM 4028 (0x0FBC) Download request only, ignoring location update ContentAccess 3/29/2019 3:29:14 AM 4028 (0x0FBC) Location update from CTM for content LIB00003.15 and request {9E0C4E3D-1981-4E35-8872-22BDDEED324F} ContentAccess 3/29/2019 3:29:14 AM 7276 (0x1C6C) Download request only, ignoring location update ContentAccess 3/29/2019 3:29:14 AM 7276 (0x1C6C) Location update from CTM for content Content_6a919932-b12f-46e1-be00-73c7d9c33269.1 and request {FF212273-2733-494F-87EE-33D06D76368A} ContentAccess 3/29/2019 3:29:14 AM 3856 (0x0F10) Download request only, ignoring location update ContentAccess 3/29/2019 3:29:14 AM 3856 (0x0F10) Location update from CTM for content Content_f7c36f23-6552-4ba8-b79c-2fb0d0a6463f.1 and request {CAEC8A21-7228-465F-80BC-BE1833D7321C} ContentAccess 3/29/2019 3:29:14 AM 4028 (0x0FBC) Download request only, ignoring location update ContentAccess 3/29/2019 3:29:14 AM 4028 (0x0FBC) Location update from CTM for content Content_9fca0c3a-abb4-45cf-8607-9002e09ff55d.1 and request {5BE028BD-31EF-40D7-ACCC-B68B5EAB238A} ContentAccess 3/29/2019 4:29:13 AM 8668 (0x21DC) Download request only, ignoring location update ContentAccess 3/29/2019 4:29:13 AM 8668 (0x21DC) Location update from CTM for content Content_f71ec7c6-8d83-4cff-baed-d042bee249db.1 and request {D933FF2F-430E-4AA3-9B2C-061131DA6764} ContentAccess 3/29/2019 4:29:13 AM 8668 (0x21DC) Download request only, ignoring location update ContentAccess 3/29/2019 4:29:13 AM 8668 (0x21DC) Location update from CTM for content Content_79793beb-8d31-491e-b97d-6e83188fa407.1 and request {3E6E2FEA-A93F-4642-9B18-B8006B334F95} ContentAccess 3/29/2019 4:29:13 AM 9084 (0x237C) Download request only, ignoring location update ContentAccess 3/29/2019 4:29:13 AM 9084 (0x237C) Location update from CTM for content Content_5354c64f-945a-4b08-a003-064130a4566a.1 and request {AEF8926C-5624-4BC0-B24F-1B7D4758212D} ContentAccess 3/29/2019 4:29:13 AM 7276 (0x1C6C) Download request only, ignoring location update ContentAccess 3/29/2019 4:29:13 AM 7276 (0x1C6C) Location update from CTM for content Content_3bea231e-1c77-4cda-8026-85eebee83451.1 and request {FA24E938-E4C0-4B3D-B0B8-ABD927785070} ContentAccess 3/29/2019 4:29:13 AM 4904 (0x1328) Download request only, ignoring location update ContentAccess 3/29/2019 4:29:13 AM 4904 (0x1328) Location update from CTM for content Content_637b724f-2a10-4111-9ca0-b0583587edaa.1 and request {F1AD0338-79E5-43B8-A996-D0E573C57A97} ContentAccess 3/29/2019 4:29:13 AM 8668 (0x21DC) Download request only, ignoring location update ContentAccess 3/29/2019 4:29:13 AM 8668 (0x21DC) Location update from CTM for content LIB00003.15 and request {9E0C4E3D-1981-4E35-8872-22BDDEED324F} ContentAccess 3/29/2019 4:29:13 AM 4904 (0x1328) Download request only, ignoring location update ContentAccess 3/29/2019 4:29:13 AM 4904 (0x1328) Location update from CTM for content Content_6a919932-b12f-46e1-be00-73c7d9c33269.1 and request {FF212273-2733-494F-87EE-33D06D76368A} ContentAccess 3/29/2019 4:29:14 AM 4904 (0x1328) Download request only, ignoring location update ContentAccess 3/29/2019 4:29:14 AM 4904 (0x1328) Location update from CTM for content Content_f7c36f23-6552-4ba8-b79c-2fb0d0a6463f.1 and request {CAEC8A21-7228-465F-80BC-BE1833D7321C} ContentAccess 3/29/2019 4:29:14 AM 7596 (0x1DAC) Download request only, ignoring location update ContentAccess 3/29/2019 4:29:14 AM 7596 (0x1DAC) Location update from CTM for content Content_9fca0c3a-abb4-45cf-8607-9002e09ff55d.1 and request {5BE028BD-31EF-40D7-ACCC-B68B5EAB238A} ContentAccess 3/29/2019 5:29:13 AM 7708 (0x1E1C) Download request only, ignoring location update ContentAccess 3/29/2019 5:29:13 AM 7708 (0x1E1C) Location update from CTM for content Content_f71ec7c6-8d83-4cff-baed-d042bee249db.1 and request {D933FF2F-430E-4AA3-9B2C-061131DA6764} ContentAccess 3/29/2019 5:29:13 AM 7708 (0x1E1C) Download request only, ignoring location update ContentAccess 3/29/2019 5:29:13 AM 7708 (0x1E1C) Location update from CTM for content Content_79793beb-8d31-491e-b97d-6e83188fa407.1 and request {3E6E2FEA-A93F-4642-9B18-B8006B334F95} ContentAccess 3/29/2019 5:29:13 AM 5440 (0x1540) Download request only, ignoring location update ContentAccess 3/29/2019 5:29:13 AM 5440 (0x1540) Location update from CTM for content Content_5354c64f-945a-4b08-a003-064130a4566a.1 and request {AEF8926C-5624-4BC0-B24F-1B7D4758212D} ContentAccess 3/29/2019 5:29:13 AM 5440 (0x1540) Download request only, ignoring location update ContentAccess 3/29/2019 5:29:13 AM 5440 (0x1540) Location update from CTM for content Content_3bea231e-1c77-4cda-8026-85eebee83451.1 and request {FA24E938-E4C0-4B3D-B0B8-ABD927785070} ContentAccess 3/29/2019 5:29:14 AM 5440 (0x1540) Download request only, ignoring location update ContentAccess 3/29/2019 5:29:14 AM 5440 (0x1540) Location update from CTM for content Content_637b724f-2a10-4111-9ca0-b0583587edaa.1 and request {F1AD0338-79E5-43B8-A996-D0E573C57A97} ContentAccess 3/29/2019 5:29:14 AM 5440 (0x1540) Download request only, ignoring location update ContentAccess 3/29/2019 5:29:14 AM 5440 (0x1540) Location update from CTM for content LIB00003.15 and request {9E0C4E3D-1981-4E35-8872-22BDDEED324F} ContentAccess 3/29/2019 5:29:14 AM 7708 (0x1E1C) Download request only, ignoring location update ContentAccess 3/29/2019 5:29:14 AM 7708 (0x1E1C) Location update from CTM for content Content_6a919932-b12f-46e1-be00-73c7d9c33269.1 and request {FF212273-2733-494F-87EE-33D06D76368A} ContentAccess 3/29/2019 5:29:14 AM 8668 (0x21DC) Download request only, ignoring location update ContentAccess 3/29/2019 5:29:14 AM 8668 (0x21DC) Location update from CTM for content Content_f7c36f23-6552-4ba8-b79c-2fb0d0a6463f.1 and request {CAEC8A21-7228-465F-80BC-BE1833D7321C} ContentAccess 3/29/2019 5:29:14 AM 7708 (0x1E1C) Download request only, ignoring location update ContentAccess 3/29/2019 5:29:14 AM 7708 (0x1E1C) Location update from CTM for content Content_9fca0c3a-abb4-45cf-8607-9002e09ff55d.1 and request {5BE028BD-31EF-40D7-ACCC-B68B5EAB238A} ContentAccess 3/29/2019 6:29:13 AM 6536 (0x1988) Download request only, ignoring location update ContentAccess 3/29/2019 6:29:13 AM 6536 (0x1988) Location update from CTM for content Content_f71ec7c6-8d83-4cff-baed-d042bee249db.1 and request {D933FF2F-430E-4AA3-9B2C-061131DA6764} ContentAccess 3/29/2019 6:29:13 AM 7728 (0x1E30) Download request only, ignoring location update ContentAccess 3/29/2019 6:29:13 AM 7728 (0x1E30) Location update from CTM for content Content_79793beb-8d31-491e-b97d-6e83188fa407.1 and request {3E6E2FEA-A93F-4642-9B18-B8006B334F95} ContentAccess 3/29/2019 6:29:13 AM 7728 (0x1E30) Download request only, ignoring location update ContentAccess 3/29/2019 6:29:13 AM 7728 (0x1E30) Location update from CTM for content Content_5354c64f-945a-4b08-a003-064130a4566a.1 and request {AEF8926C-5624-4BC0-B24F-1B7D4758212D} ContentAccess 3/29/2019 6:29:14 AM 7728 (0x1E30) Download request only, ignoring location update ContentAccess 3/29/2019 6:29:14 AM 77 I've also checked the boundaries and boundary groups to ensure that the correct network is in there. Other stuff: DP is HTTPS enabled, "allow intranet-only connections", using a PKI certificate, MP is HTTPS enabled "allow intranet-only connections" as well. Wireless clients are domain joined, and all of these application deployments work fine on wired clients. Any help where to look is appreciated!
  24. Hello, I've deployed a group of Windows updates to a collection which has no maintenance window and it's works correcty and all devices are comliant excep one who do not getting the updates and showing "Client check passed/Active" state. I've tried to stop wuauserv service and delete "SoftwareDistribution" floder but it isn't works for me. below details about my environment. Client Device : windows Server 2012 R2 whitch hosts the McAfee antivirus solution. FYI: I've tried to stop McAfee services but it restart automaticaly when the process of updates begin. SCCM Management Server: SCCM 2012 R2 SP1, WSUS 4.0 (6.3.9600.18694) Logs : - WUAHandler.log : Successfully completed scan - UpdatesDeployment.log : EnumerateUpdates for action (UpdateActionInstall) - Total actionable updates = 0 - LocationServices.log : ALL its correct - WindowsUpdate.log : 4 Warning WARNING: IsSessionRemote: WinStationQueryInformationW(WTSIsRemoteSession) failed for session 9, GetLastError=2250 WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80240037 WARNING: Failed to initialize event uploader for new server {9482F4B4-E343-43B6-B170-9A65BC822C77} with hr = 8024043d. WARNING: Network Cost is assumed to be not supported as something failed with trying to get handles to wcmapi.dll Thank you in advance for your help. cordially. Hadjer YAHIAOUI Infra Admin
  25. 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.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.