Jump to content


Search the Community

Showing results for tags 'SCCM'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • 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
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • 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


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 652 results

  1. Team, In a recent Security Audit at my workplace , it was found that SSLv3 was enabled on IBCM server. We need to disable SSLv3 , TLSv1 & enable TLSv1.2 . Did anybody done this… Kindly share your Observations.. Also, Any Support article, guide will be of great help. I have done the changes as per reading on Internet under... HKey_Local_MachineSystemCurrentControlSetControlSecurityProviders SCHANNELProtocols Now, my Internet Based clients are not communicating to IBCM server at all. No Policy since the changes made.. Kindly suggest..
  2. Hello, hoping for some help from with a strange issue I have on a customer site I am currently unable to build Dell Optiplex 5040 devices with Windows 10 1909 x64 Enterprise from an Endpoint manager 1910 MDT integrated task sequence. The task sequence fails when trying to execute the Invoke-MbamClientDeployment.ps1 script. I have detailed the high level tasks below and attached the SMSTS.log. BIOS upgraded to latest version BIOS Reset to factory settings BIOS Password Set BIOS Standard config applied UEFI Boot enabled TPM Cleared & activated TPM Converted from 1.2 to 2.0 TPM Cleared again and reactivated OS Deployed Drivers deployed MBAM TPMPassTheHash step completed DOTNET Enabled C++ Redists applied Security Patches Applied The MBAM Group MBAM_XTS_AES256 applied to reg PreBoot Input Protectors for Tablets applied to reg MDOP MBAM 2.5 SP1 Installed MBAM Client Hot Fix KB4505175 Applied Sleep 2 mins DisableRootAutoUpdate (Certificate applied) Restart Set PowerShell Execution Policy Set to bypass Set PowerShell Execution Policy powershell.exe -command Initialize-TPM Is run **THE STEP THAT FAILS** Invoke-MbamClientDeployment.ps1 with the below parameters Parameters - -RecoveryServiceEndpoint "https://MBAM:443/MBAMRecoveryAndHardwareService/CoreService.svc" -StatusReportingServiceEndpoint "https://MBAM:443/MBAMComplianceStatusService/StatusReportingService.svc" –IgnoreEscrowOwnerAuthFailure -EncryptionMethod "XTSAES256" **The Post Steps** Reset TPM Policy EnableRootAutoUpdate The TPM status is Enabled, Activate & NOT owned The above works on all other models tested but fails on the 5040 The actual error message received is contained in the smsts.log file attached and the extract is below. The device is also in a staging OU that receives no Group Policy. The device does register in MBAM if continue on error is checked on the offending task and the computer object moved to the correct OU but will not encrypt. The same task sequence works on the other Dell models tested e.g. 5050 I have logged in after and BitLocker throws a internal error if you try to run it manually. **THE ENVIRONMENT**** A single site deployment of Endpoint Manager 1910 with two distribution points deploying Windows 10 1909 x64 enterprise with a MDT Integrated task sequence. The Dell command tool kit has been integrated into End Point Manager and drives the BIOS/TPM config steps in the task sequence. The Dell TPM conversion tool is used to convert the TPM to 2.0. The devices been build are production Windows 7 and are been repurposed as Windows 10 x64 Enterprise 1909
  3. Version française Bonjour, J'ai un petit problème quand je veut afficher un rapport de logiciel . Il m'est impossible de sélectionnez le mois et l’année affin de générer le rapport : Version english Hello, I have a little problem when I want to view a software report. I am unable to select the month and year in order to generate the report:
  4. In a previous series of guides I showed you how to configure PKI in a lab on Windows Server 2016. In another series, I also showed you how to install System Center Configuration Manager (Current Branch) version 1802 on Windows Server 2016 with SQL Server 2017. In this lab, I will show you how to configure SCCM to utilize that PKI environment. This series is based upon an excellent video by the talented former Microsoft Premier Field Engineer Justin Chalfant here. If you haven't seen it yet, do check it out. The intention here is that after you've completed this PKI enabled SCCM lab you can then use this in future guides, and to dig deeper into new technologies from Microsoft, for example enabling a Cloud Management Gateway and/or Cloud Distribution Point and using later on, using Co-Management. Note: To complete this lab you must first complete the PKI Lab series (8 parts) and then install a new virtual machine within that PKI lab running System Center Configuration Manager (Current Branch) version 1902 utilizing this series, that installation of Configuration Manager will be in HTTP mode. In addition, you must configure the Software Update Point role (in HTTP mode) on CM01 See this guide (step 2 onward) for details. For details how to configure that, see this post. It will take some time to setup but you'll be glad you did. Also, don't do this in production without consulting with a PKI Expert. I don't claim to be one, I'm just helping you get it up and running in a lab. This is intended for use in a lab only. Step 1 - Create an Active Directory Security Group In this step you'll create an active directory group which will contain all your site systems that use Configuration Manager server roles which utilize IIS (Internet Information Systems) such as the below (1): Management point Distribution point Software update point State migration point Enrollment point Enrollment proxy point Application Catalog web service point Application Catalog website point A certificate registration point On the Active Directory domain controller (DC01), open Active Directory Users and Computers, and expand the windowsnoob organisational unit (OU) created in this Step 1, part 5 of this blog post. Click on Security Groups, and then right click and choose New, select Group. Give the group a name, SCCM IIS Servers. Once done, right click on the SCCM IIS Servers Active Directory Security Group, choose Properties and click on the Members tab, click on Add, for Object Types make sure Computers are selected. Add the Configuration Manager server (CM01) to that group. Once done, reboot the Configuration Manager server (CM01) using the following command otherwise you might get access denied when trying to request a certificate. shutdown /r Step 2. Create certificate templates on the Issuing CA In this step you will create three new certificate templates for use within SCCM by duplicating existing templates. Using the windowsnoob\Entadmin credentials, logon to the Issuing CA server (IssuingCA) and launch the certificate authority console (CertSrv.msc). In the three templates below, one uses the Web Server template, and the others use the Workstation Authentication template, you can verify which Microsoft certificate template to use by using the tables on the following blog post, of which i'm showing a screenshot below to make it clear. 1. SCCM IIS Certificate Right click on Certificate Templates and choose Manage. Scroll down to Web Server from the templates listed. Right click on the Web Server template and choose Duplicate Template. The Properties of New Template screen appears. Verify that the Certificate Authority Compatibility settings are set to Windows Server 2003. Note: When you use an enterprise certification authority and certificate templates, do not use the Version 3 templates. These certificate templates create certificates that are incompatible with System Center Configuration Manager. Instead, use Version 2 templates by using the following instructions. On the Compatibility tab of the certificate template properties, specify Windows Server 2003 for the Certification Authority option, and Windows XP / Server 2003 for the Certificate recipient option. (1) Click on the General tab and rename it to SCCM IIS Certificate. On the Request Handling tab, verify that Allow private key to be exported is not selected (default). On the Subject Name tab verify that the Supply in the Request is selected (default). On the Security tab, add the previously created Active Directory Security Group called SCCM IIS Servers and give it Read and Enroll access. Optionally you can remove Enroll from the Domain Admin and Enterprise Admins as it is mentioned in the docs. Click Apply to apply the changes and then close the Properties of New Template. 2. SCCM DP Certificate This template is used by the distribution point site system for Operating System Deployment (clients that are not domain joined). Next, right click on Workstation Authentication from the templates listed and choose Duplicate Template. The Properties of New Template screen appears. The Properties of New Template screen appears. Verify that the Certificate Authority Compatibility settings are set to Windows Server 2003. Click on the General tab and rename it to SCCM DP Certificate, change the validity period to something more reasonable, like 3 years. On the Request Handling tab, ensure that Allow private key to be exported is selected to allow us to export the certificate as a pfx file and we need the private key to do so, as we'll import that certificate into our console so that the clients can utilize it during imaging (workgroup members, to authenticate back to your site). On the Security tab, add the previously created Active Directory Security Group called SCCM IIS Servers and give it Read and Enroll access. Next, remove Domain Computers altogether. Click Apply to apply the changes and then close the Properties of New Template. 3. SCCM Client Certificate This template is used by clients to communicate with site systems. Next, right click on Workstation Authentication from the templates listed and choose Duplicate Template. The Properties of New Template screen appears. The Properties of New Template screen appears. Verify that the Certificate Authority Compatibility settings are set to Windows Server 2003. Click on the General tab and rename it to SCCM Client Certificate, change the validity period to something more reasonable, like 3 years. Under Subject Name verify that Build from Active Directory is selected. On the Request Handling tab, verify that Allow private key to be exported is not selected (default). On the Security tab, select Domain Computers and ensure that Read, Enroll and AutoEnroll permisions are selected. Click Apply to apply the changes and then close the Properties of New Template. The three SCCM templates are now shown below. Close the Certificate Templates console. Next you will issue these certificate templates. To do so, in the Certificate Authority (on the IssuingCA), right click on Certificate Templates and choose New, then Certificate Template to Issue. In the Enable Certificate Templates window, select the 3 previously created SCCM templates as shown below and click OK. They will now appear under Certificate Templates. Step 3. Verify Auto-Enrollment GPO is enabled for the Client Certificate In Part 8 of the PKI lab you enabled Auto Enrollment so that clients can request certificates automatically. As it is a lab, the setting is deployed in the default domain GPO. The setting is in Computer Configuration, Policies, Windows Settings, Security Settings, Public Key Policies, and Certificate Services Client - Auto Enrollment. The setting should look like so (Enabled). Step 4. Requesting the IIS and DP/OSD Certificates on the IIS Site System On the SCCM server (CM01), which hosts all those IIS ConfigMgr roles, start certlm.msc from an Administrative command prompt. if you expand Personal, then Certificates, you'll see certificates issued to that computer, there will be a few by default. In the administrative command prompt, run gpupdate /force to pull down group policy changes...and refresh the view in certlm. Below you can see the SCCM Client Certificate template was used to generate this Client Authentication certificate. Requesting New certificates Next, you will request certificates from Active Directory, to do so, right click on Certificates and choose All Tasks then Request New Certificate. click Next at the Before you begin screen, and verify that Active Directory Enrollment Policy is selected before clicking Next. Select the SCCM DP Certificate and SCCM IIS Certificate from those listed (you already have the SCCM Client Certificate from AutoEnrollment). You'll notice that for the SCCM IIS Certificate, more information is required to enroll, Click on the message to enter this info. For Alternative Name, choose the DNS option and then click on Add to add the hostname and fully qualified domain name of your SCCM server (CM01). Note: If you want this server to be available via IBCM you could also add the publicly available FQDN of the site here (eg: cm01.windowsnoob.com) Next Click on General, and give this cert a friendly name so we can distinguish it in IIS later when we bind it. click OK, then click Enroll. It should state a status of Succeeded for both certificates. If not look at the details to find out what went wrong. Click Finish to exit. Exporting the Distribution Point certificate Next you need to export the Distribution Point certificate so that during OSD the client can authenticate to the management point in WinPE. To do that, refresh the view in Certificates (certlm.msc) and then select the client authentication certificate created with the SCCM DP Certificate template. Right click and choose All Tasks, then select Export. In the welcome to certificate export wizard click Next and choose to export the private key. stick with the defaults and give it a password that you will use when you import it back into the SCCM Console, I used P@ssw0rd Save the cert to your desktop. and continue through that wizard until completion. You should see that the export was successful. That's it for this part, please join me in part 2 where we will complete the configuration of SCCM to HTTPS. cheers niall Recommended reading (1) - https://docs.microsoft.com/en-us/sccm/core/plan-design/network/pki-certificate-requirements
  5. I have done the cleaning up of WSUS Database and Re-add the classification but the problem still persist. The IIS application pool service is running and the SCCM is not able to connect to the WSUS server. What should i do? I think SCCM is having some other issues. Im encountering some errors in the component which is in critical status. I have also tried uninstall the WSUS and SUP but still no luck. Critical SMS_WSUS_SYNC_MANAGER SCCMSERVER.SCCM1.LOCAL Monitored Thread Component SCC Online Critical SMS_WSUS_CONTROL_MANAGER SCCMSERVER.SCCM1.LOCAL Monitored Thread Component SCC Unknown Critical SMS_WSUS_CONFIGURATION_MANAGER SCCMSERVER.SCCM1.LOCAL Monitored Thread Component SCC Online The logs for WCM log Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608) SMS_WSUS_CONFIGURATION_MANAGER 5/18/2020 2:16:34 PM 6688 (0x1A20) Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER 5/18/2020 2:16:34 PM 6688 (0x1A20) Did not find supported version of assembly Microsoft.UpdateServices.Administration. SMS_WSUS_CONFIGURATION_MANAGER 5/18/2020 2:16:34 PM 6688 (0x1A20) Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER 5/18/2020 2:16:34 PM 6688 (0x1A20) Failed to create assembly name object for Microsoft.UpdateServices.Administration. Error = 0x80131701. SMS_WSUS_CONFIGURATION_MANAGER 5/18/2020 2:16:34 PM 6688 (0x1A20) Supported WSUS version not found SMS_WSUS_CONFIGURATION_MANAGER 5/18/2020 2:16:34 PM 6688 (0x1A20) STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=SCCMSERVER.SCCM1.LOCAL SITE=SCC PID=6672 TID=6688 GMTDATE=Mon May 18 06:16:34.424 2020 ISTR0="SCCMSERVER.SCCM1.Local" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER 5/18/2020 2:16:34 PM 6688 (0x1A20) Remote configuration failed on WSUS Server. SMS_WSUS_CONFIGURATION_MANAGER 5/18/2020 2:16:34 PM 6688 (0x1A20) Here is the wsyncmgr log Read SUPs from SCF for SCCMSERVER.SCCM1.Local SMS_WSUS_SYNC_MANAGER 5/18/2020 2:00:01 PM 3660 (0x0E4C) Found 1 SUPs SMS_WSUS_SYNC_MANAGER 5/18/2020 2:00:01 PM 3660 (0x0E4C)Found active SUP SCCMSERVER.SCCM1.Local from SCF File. SMS_WSUS_SYNC_MANAGER 5/18/2020 2:00:01 PM 3660 (0x0E4C) DB Server not detected for SUP SCCMSERVER.SCCM1.Local from SCF File. skipping. SMS_WSUS_SYNC_MANAGER 5/18/2020 2:00:01 PM 3660 (0x0E4C) Sync failed: WSUS update source not found on site SCC. Please refer to WCM.log for configuration error details.. Source: getSiteUpdateSource SMS_WSUS_SYNC_MANAGER 5/18/2020 2:00:01 PM 3660 (0x0E4C) STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SCCMSERVER.SCCM1.LOCAL SITE=SCC PID=6672 TID=3660 GMTDATE=Mon May 18 06:00:01.071 2020 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site SCC. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_SYNC_MANAGER 5/18/2020 2:00:01 PM 3660 (0x0E4C) Setting sync alert to active state on site SCC SMS_WSUS_SYNC_MANAGER 5/18/2020 2:00:01 PM 3660 (0x0E4C)Sync time: 0d00h00m00s SMS_WSUS_SYNC_MANAGER 5/18/2020 2:00:01 PM 3660 (0x0E4C)Skipping Delete Expired Update relations since this is not a scheduled sync. SMS_WSUS_SYNC_MANAGER 5/18/2020 2:00:01 PM 3660 (0x0E4C)Inbox source is local on SCCMSERVER.SCCM1.Local SMS_WSUS_SYNC_MANAGER 5/18/2020 2:00:01 PM 3660 (0x0E4C) I have restart some of the SCCM services in service.msi (couldn't find all services inside) but SCCM is not running correctly. The WSUS is installed in add roles and features Windows Server 2016, but i really doesn't know why it cannot detect my WSUS on which installed in another server. So do i need to reinstall the SCCM console again? May any kind souls please enlighten me. Thank You
  6. Introduction This multi-part guide will show you how to install the latest baseline version of Configuration Manager from Microsoft. The latest available baseline version at the time of writing is System Center Configuration Manager (Current Branch) version 1902. SCCM 1902 is the latest baseline version and contains many bugfixes (and quality fixes) as detailed here. I blogged how to upgrade to 1902 here. Baseline media is used to install new ConfigMgr sites or to upgrade from supported versions. For more information about what baseline versions are and why you need them, I'd recommend you read my blog post here. This guide is aimed a new installations of SCCM. This lab is one of many hosted on my new hyper-v host, which is a very nice Lenovo P1 running Windows Server 2019 with data deduplication to make storage amazing. Note: The SCCM 1902 Current Branch media is available on MSDN or VLSC. If you don't have access to either of those you can download the baseline media ISO from the Microsoft evaluation site here. This is the same media that is on MSDN and VLSC. Once downloaded, extract the media to C:\Source\SCCM1902. This series is broken down into the following parts:- Part 1 - Get the lab ready, configure ADDS (this part) Part 2 - Join CM01 to Domain, add users, create the Systems Management container, delegate permission Part 3 - Role and Feature installation, installation of WDS and ADK Part 4 - Configure and install SQL Server 2017 Part 5 - Configure and install SCCM 1902 Current Branch Part 6 - Create device collections Part 7 - Configuring discovery Part 8 - Configuring boundaries You can use this multi-part guide to get a hierarchy up and running on Windows Server 2019 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 Downloads The scripts used in this part of the guide are available for download here. Unzip to C:\Scripts. The scripts are placed in the corresponding folder (Part 1, Part 2 etc) and sorted into which server you should run the script on (DC01 or CM01). Scripts.zip Step 1. Get your lab ready In this guide I assume you have already installed two WorkGroup joined servers with Windows Server 2019 Standard (Desktop Experience) installed. You can install the operating system on those servers in whatever way you want. If you want a PowerShell script to help you create hyper-v virtual machines you can use this one. Please configure the servers used in this guide as listed below, the SmoothWall (Linux firewall) is optional. Server function: Domain Controller Server name: DC01 Server info: Workgroup joined IPv4 Address: 192.168.9.1 Subnet Mask: 255.255.255.0 Default Gateway: 192.168.9.199 DNS: 192.168.9.1 Server function: Configuration Manager Primary site Server Name: CM01 Server info: Workgroup joined IPv4 Address: 192.168.9.2 Subnet Mask: 255.255.255.0 Default Gateway: 192.168.9.199 DNS: 192.168.9.1 Server function: (optional) Linux firewall Server name: smoothwall Server info: Uses 2 legacy nics eth0: 192.168.9.199 eth1: x.x.x.x (internet facing ip) You will also need the following media. Windows Server 2019 Standard SQL Server 2017 System Center Configuration Manager 1902 Current Branch Step 2. Configure Active Directory Domain Services (ADDS) To setup Active Directory Domain Services you could manually click your way through the appropriate wizard in Server Manager or automate it using PowerShell. For your benefit I'll show you both methods below, all you have to do is choose which one suits you. Method #1 - Do it manually On the DC01, open Server Manager. Click on Add roles and features On the Before You Begin screen click Next. For Installation Type select Role-based or Feature-based installation For Server Selection select Select a server from the server pool and choose DC01 For Server Roles select Active Directory Domain Services, when prompted to add features that are required for Active Directory Domain Services select Add Features select DHCP Server,when prompted to add features that are required for DHCP Server, accept the changes by clicking on Add Features Select DNS Server, when prompted to add features that are required for DNS Server, accept the changes by clicking on Add Features Continue the the wizard by clicking Next On the Features screen click Next On the AD DS screen click Next On the DHCP server screen, click Next On the DNS Server screen click Next On the Confirmation screen click Install and then click on Close Configure Post Deployment Configuration After it's finished, perform the Post Deployment Configuration by clicking on Promote this server to a domain controller select the Add a new forest option, give it a root domain name such as windowsnoob.lab.local Next, depending on your requirements set the Forest functional level and Domain functional level, I've selected the default options below however you may want to configure it differently for your hierarchy, For the password field use P@ssw0rd, Click Next when ready, for DNS options, click Next, Next verify the NetBIOS name and click Next To specify the location of the AD DS database, log files and so forth, either accept the defaults, or change them to something that suits your hierarchy and click Next. Next you can review the options (clicking view script will save your actions to a PowerShell script for use later if you wish). Click Next when done. Next, click Install to begin Once it is complete making the changes it will automatically reboot the server After the reboot, open Server Manager again to do the Post-deployment Configuration for DHCP Server. Click on Complete DHCP Configuration use the defaults for DHCP Server Authorization Click on Commit, Click Close when done. That's how to configure ADDS and DHCP manually. Method #2 - Automate it with PowerShell To configure ADDS, DNS and DHCP automatically, use the ConfigureADDS.ps1 PowerShell script. Note: I'd recommend that you reboot the server before running the script in case any pending operations like Windows Update are in progress as it may effect the results of the script below - I have not (yet) added in any detection for pending operations. 1. Copy the script to C:\scripts on DC01 2. Edit the variables in lines 17-32 as desired before running. 3. Start Windows PowerShell ISE as Administrator and run the script by clicking on the green triangle. Once the script is run, it will automatically reboot the server, and after you logon, it will complete the DHCP server installation. Summary Using PowerShell to automate things is the proper way to do things as a server admin. Please join me in Part 2 of this multi-part guide where you will continue setting up your new Windows Server 2019 lab with SCCM 1902 Current Branch.
  7. Hi All, Currently managing SCCM infrastructure for K-12 School District. Since we are currently on stay at home orders, I've researched Cloud Management Gateway to be able to patch / deploy software to clients over the internet. We have very few concurrent VPN licenses and the client is not installed on everyone's machine. All Devices are already Hybrid Azure Joined through SCCM. I successfully setup CMG using a cloudapp.net address... IF a user connects through VPN, their client will update and then CMG works great! So my question is as follows: How can I get clients to update to use CMG while users are at home and can't VPN in to get the client settings update? Any advice appreciated. Thank you
  8. I am currently managing 2 companies that have a 2 way domain trust. These companies are sister companies but have separated infrastructure. They each have their own network; physical and logical, domain controllers, etc. I installed SCCM on Domain A and currently do not have infrastructure setup to install SCCM on Domain B so initially I setup SCCM with HTTP but moved to PKI/HTTPS last week. Everything on Domain A is going well but today all systems in Domain B have become unmanageable which I found out when troubleshooting installing the SCCM client on a VM in Azure on Domain B. I need help on how to get Domain B to be managed via SCCM from Domain A. I have setup PKI on both domains but I am getting errors related to Certs/IIS. Well from what I have researched it is but all the solutions in my research only apply to SCCM on 1 domain, not multi-domains. The 2 domains can traverse over the network to access other network resources like a file share for an example. Therefor I know connectivity is there between the 2. Now this is where my ignorance kicks in. I setup SCCM with Trusted Root Certificate Authorities on the Communication Security tab in Administration>Site Configuration>Sites>Properties. I specified Domain A CA and created Certificate profiles in Assets and Compliance. I have since removed them to see if that resolved my issue but it has not so I am debating if I configure this again or not. I decided I will review that at a later date. I have attached the log from ccmsetup.exe that failed on the VM on Domain B. If anyone could help, I would greatly appreciate it as I am trying to manage all systems in both domains remotely because of Covid-19. In an ideal world I would prefer to have infrastructure in place for me to have SCCM on both domains, installed and disregard the cross-forest/domain setup but there are no more money trees to pick from. Thank you in advance!! If you need further information from me, please let me know. ccmsetup.log
  9. We have some Dell Optiplex 7070 computers, and I'm trying to deploy a Windows 10 1909 image to them without changing the default bios configuration, which comes set to "Raid On" in Sata Operation. The default dell image works fine, so I'm not sure why ours does not. I'm imported all of the drivers that I could find for this model and intel storage in general. The task applies the OS and works in winPE fine, but after rebooting just gets a blue screen. How do I get this working? Thanks
  10. 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/
  11. 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
  12. Hi, I am looking for a way to determine which client settings my SCCM client currently is using. The context of this question is that I have build a (hybrid) cloud deployment workflow, and as part of the workflow I am triggering several sccm actions. Condition for these actions is that the client has loaded its specific client settings, which are assigned based on a dynamic collection. I already have checks that the client is listed as member of the collection, but since initial processing of client settings take some time (and incidentally fails the first time which results in the default client settings being loaded) I need a check to determine which client settings are active on the client. I'd prefer to check it on the client (but am open to alternative possibilities) and to be able to do the check with powershell is a must (since the check if part of a workflow), I cant however seem to find where to find info on the active client settings. Possible scenarios I have in mind are: When proper client settings are loaded, we have a specific title in software center. If i can find where I can query this title with a script, I can determine the active client settings. If (and i would assume so) there is any info in the SCCM clients WMI space about the processed client settings or software center title, that would be great and easy to check. However I haven't been able to find where in the WMI space there is such info. If SCCM console somewhere in the device info what settings have been processed by the client, I could check that. Least desirable, but if this info is somewhere in the SCCM Database, I can check that. I hope my question is clear and somebody is able to help me out or give some pointers on where to find detailed info on processed client settings. Thanks in advance! [EDIT] I wasnt sure which category to pick, so if "collections" isnt the best option, my apologies
  13. 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
  14. 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.
  15. 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
  16. 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.
  17. 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
  18. 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).
  19. 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
  20. 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?
  21. 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?
  22. Can a google chrome extension be added as part of a packaged installer along with the msi
  23. 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?
  24. 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
  25. 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.
×
×
  • Create New...