All Activity
This stream auto-updates
- Last week
-
We found the solution. In SCCM 1806 CB there is a new feature you can adjust. Go to Administration - Hierarchy Configuration - Boundary Groups Open a boundary group and go to the tab Options We unchecked the "allow peer......." checkbox After this all App-v packages streamed very fast. The explination of this is that we use the App-V packages in stream mode. But when you enable this option a workspace will look for all other workspaces who installed the package. So it tries to install the package form another workspace instead of the SCCM DP. Because we stream a App-v package there is no packages at de local cache to install. So there the waiting begins. When you monitor the VirtualApp.log on the workspace you can see alle the other workspaces it tries to communicate with. I think this is a bug because if you are using App-v in streaming mode this option should be unmarked by default. -
ITNINJAGUY, thanks for posting the resolution!! -
good work, thanks for the updates and the fix for that scenario ! -
Fix for bootloops when a TS is initiated from Software Center and the script is detecting failures during the checks. Change Sub Reboot Set WshShell = WScript.CreateObject("WScript.Shell") WshShell.Run "wpeutil reboot" End Sub To Sub Reboot Set objFSO2 = CreateObject("Scripting.FileSystemObject") Set colDrives = objFSO2.Drives For Each objDrive in colDrives if objDrive.DriveType=2 then SMSTSDrive=objFSO2.FolderExists(objDrive.DriveLetter + ":\_SMSTaskSequence") if SMSTSDrive then BootDrive=objDrive.DriveLetter&":\" end if end if Next Set WshShell = WScript.CreateObject("WScript.Shell") PEFirmware="HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PEFirmwareType" PeBoot = "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PEBootType" FirmwareType=WshShell.RegRead(PEFirmware) BootType=WshShell.RegRead(PeBoot) If lcase(BootType)="ramdisk:sourceidentified" then If FirmwareType=2 then BCD=BootDrive&"_SMSTaskSequence\BCD-EFI\BCD" else BCD=BootDrive&"_SMSTaskSequence\backup\boot\BCD" end if WshShell.Run("bcdedit /import " & BCD & " /clean"),1,true wscript.sleep(2000) end if WshShell.Run "wpeutil reboot" End Sub This will also cause the TS to continue in the full OS. If you want to prevent that add something like this after the first reboot. (Since checkfornetwork.vbs shouldn't fail if it succeeded the first time) Side note. The start cmd part is good but it's a LPE-exploit waiting to happen. All you have to do is start a TS from SC and then pull the cable and you're 'local system'. Don't bind it to cancel since the x in the corner returns the same thing. Detect if "command support" is enabled on the boot image and only give the choice to start a cmd.exe if so. Add the last 2 lines accordingly. ' updated 2015/4/26 logging folder creation fix ' On Error Resume Next DIM objShell, WshNetwork, sPingTarget, iNumberofFails, iFailureLimit, LogFileName, logfile, objFSO, objFile, outFile, CheckPartitions Set WshNetwork = WScript.CreateObject("WScript.Network") Set objShell = WScript.CreateObject( "WScript.Shell" ) sysDrv=objShell.ExpandEnvironmentStrings( "%SYSTEMDRIVE%" ) Buttons=vbOKOnly And this. function isDebug() FoundINI=objFSO.FileExists(sysdrv+"\Windows\System32\winpeshl.ini") If (FoundINI=vbTrue) then 'wscript.echo Cstr(bExists) & " " & bExists Set file = objFSO.OpenTextFile (sysdrv+"\Windows\System32\winpeshl.ini", 1, vbFalse, -1) row = 0 Do Until file.AtEndOfStream line = file.Readline 'WScript.Echo lcase(line) If (instr(lcase(line),"tsbootshell.exe")<>0) then TsBootShell=replace(lcase(line),"tsbootshell.exe","tsbootshell.ini") 'Wscript.echo TsBootShell TsINI=objFSO.FileExists(objShell.ExpandEnvironmentStrings(TsBootShell)) If (TsINI=vbTrue) then Set ReadTsINI = objFSO.OpenTextFile (objShell.ExpandEnvironmentStrings(TsBootShell), 1, vbFalse, -1) strTSINItext=ReadTsINI.readall If (instr(lcase(strTSINItext),lcase("EnableDebugShell=true"))<>0) then 'WScript.Echo "DebugMode" Buttons=vbYESNO end if ReadTsINI.Close end if end if row = row + 1 Loop file.Close end if end function Add a 'If' on the buttons shown and that's been taken care of as well. E.g. if (Buttons=vbOKOnly) then Message="Kunde inte hitta en hårddisk att installera Windows på." & vbCrLf & vbCrLf & " Meddela IT att detta kan vara orsaken:" & vbCrLf & vbCrLf & "* Saknar drivrutiner för hårddisken . " & vbCrLf & "* Hårddisken kan vara trasig. " & vbCrLf & vbCrLf & "Hårdvara: " & vbCrLf & vbCrLf & SataResult &"Dator: "& MakeModel & vbCrLf & vbCrLf & "Tryck [OK] när du är klar." Else Message="Kunde inte hitta en hårddisk att installera Windows på." & vbCrLf & vbCrLf & " Meddela IT att detta kan vara orsaken:" & vbCrLf & vbCrLf & "* Saknar drivrutiner för hårddisken . " & vbCrLf & "* Hårddisken kan vara trasig. " & vbCrLf & vbCrLf & "Hårdvara: " & vbCrLf & vbCrLf & SataResult &"Dator: "& MakeModel & vbCrLf & vbCrLf & "Tryck [YES] för att få installationen att misslyckas eller [NO] för att starta en CMD-prompt." end if result=MsgBox (Message, Buttons, "Warning: Unable to continue") 'result = MsgBox ("Unable to find a valid internal storage device." & vbCrLf & vbCrLf & "Possible causes can be: " & vbCrLf & vbCrLf & "* Missing Storage drivers. " & vbCrLf & "* Missing HDD/SSD. " & vbCrLf & vbCrLf & "Please inform the person supporting you that the following hardware was detected: " & vbCrLf & vbCrLf & SataResult &"Computer: "& MakeModel & vbCrLf & vbCrLf & "Press [OK] to exit and reboot or press [Cancel] to open a CMD prompt to troubleshoot further."_ ', vbOKCancel, "Warning: Unable to continue") Select Case result Case vbOK Set objShell = Nothing 'objShell.Run("x:\windows\system32\winpeshl.exe"),1,true Reboot Case vbNo Set objShell = WScript.CreateObject( "WScript.Shell" ) objShell.Run("cmd.exe /s") msgbox "When you are finished, press [OK]" Reboot End Select Edit: And of course calling the function early in the script. -
MBAM on SCCM Server
anyweb replied to nhottinger's topic in System Center Configuration Manager (Current Branch)
i don't think so, but if you are in doubt ask your Microsoft TAM for advice. and lastly... The recommended configuration is to install the Administration and Monitoring features on one or more Microsoft BitLocker Administration and Monitoring servers, and install Microsoft System Center Configuration Manager 2007 or Microsoft System Center 2012 Configuration Manager on a separate server. from https://docs.microsoft.com/en-us/microsoft-desktop-optimization-pack/mbam-v2/deploying-mbam-with-configuration-manager-mbam2 -
MBAM on SCCM Server
nhottinger replied to nhottinger's topic in System Center Configuration Manager (Current Branch)
We have about 3000 pc's this would be used for management. Would that fall under the "large number"? -
MBAM on SCCM Server
anyweb replied to nhottinger's topic in System Center Configuration Manager (Current Branch)
depends on the size of the organization, but yes of course it can be installed on the same server, if you have a large number of clients though it's recommended you separate it onto it's own server -
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 is System Center Configuration Manager (Current Branch) version 1902 as of April the 10th 2019. I blogged how to upgrade to 1902 here. This guide is aimed a new installations of SCCM. Baseline media is used to install new ConfigMgr sites or to upgrade from supported versions, for more information about baseline media please see my blog post here. Note: The SCCM 1902 Current Branch media is not yet available on MSDN or VLSC. When the new baseline media is released I'll update this note. This series is broken down into the following parts:- Part 1 - Get the lab ready, configure ADDS 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 (This part) Part 5 - Configure and install SCCM 1902 Current Branch Part 6 - Post configuration 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. Install SQL Server 2017 Note: Perform the following on the Configuration Manager server (CM01) as a Local Administrator, I'd suggest you logon as the username matching your name. Method #1 - Do it manually In this section you will install SQL Server 2017 CU14 which is the latest supported version of SQL Server that is compatible with SCCM 1902 Current Branch as of 2019/4/16. For details about which versions of SQL Server are supported with different site systems in ConfigMgr, please see this page. Before starting, please configure the firewall as described in https://go.microsoft.com/fwlink/?linkid=94001 to allow access to SQL Server through the firewall. You can do this by executing the following command as local administrator on the CM01 (ConfigMgr) server. netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action = allow localport = 1433 remoteip = localsubnet profile = DOMAIN 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. Note: 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, as long as you've opened the correct port for SQL you'll be ok and can safely ignore the Warning about the Firewall. select the SQL server instance features you need (at least Database Engine Services) 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 (click on the Collation tab in Server Configuration), make sure the collation is set to SQL_Latin1_General_CP1_CI_AS For Database Engine 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. Next download and install the following: SQL Server 2017 Cumulative Update 14. SQL Server 2017 SSMS here. SQL Server 2017 Reporting Services. 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 set's the installation path pointing at D:\MSSQL if you want to install SQL somewhere else 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 4\CM01 2. Edit the variables [lines 17-81] as desired before running. 3. Logon as the user specified in line 20. 4. Start Windows PowerShell ISE as Administrator and run the script by clicking on the green triangle. Done ! That's it for this part, please join me in Part 5 where we Configure and Install System Center Configuration Manager 1902.
-
Been looking for some recommendations but can't find any. Can MBAM be installed directly on the SCCM server or do they need to be separated on different hardware?
-
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 is System Center Configuration Manager (Current Branch) version 1902 as of April the 10th 2019. 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. This series is broken down into the following parts:- Part 1 - Get the lab ready, configure ADDS 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 (This part) Part 4 - Configure and install SQL Server 2017 Part 5 - Configure and install SCCM 1902 Current Branch Part 6 - Post configuration 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 them 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. Install Roles and Features 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 your ConfigMgr server 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, click on Add Features when prompted. Select Message Queuing (MSMQ) Activation and when prompted select Add Features, then 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: Z:\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 2019 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 2019 installation media. 1. Extract the scripts to C:\Scripts on the ConfigMgr server, CM01 and load the install roles and features.ps1script located in C:\Scripts\Part 3\CM01 2. Edit the variables (lines 18-20) as desired before running. 3. Start Windows PowerShell ISE as Administrator and run the script by clicking on the green triangle. Tip: If the script appears to hang at 24% while installing roles and features, and if you are sure you pointed to the media path correctly then simply reboot the server and try again, chances are a pending update or another operation is blocking the installation. 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 1902 supports Windows ADK 1809 as I've explained here. Note: Since SCCM 1806, Microsoft has provided their own PXE Provider which means you can host a PXE provider on a client operating system without the need for a Server operating system (as WDS requires Windows Server). However, for the purposes of this guide, you will use Windows Deployment Services. Method #1 - Do it manually Go to this link and download ADK 1809. 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, you will need to download the Windows Preinstallation Environment (Windows PE) separately as it's no longer included with ADK 1809 and later. Deployment Tools User State Migration tool (USMT) and optionally these Imaging and Configuration Designer (ICD) Configuration Designer and click Install to start the download and Installation of the Windows ADK, version 1809. Once the ADK installation is complete, click Close. To install the Windows Preinstallation Environment (Windows PE) click here, click on Run. click Next at the Specify Location screen. click next at the Privacy settings Click Next at the License agreement and click Install when prompted. Click Close when done (this will take a while to download...). To install Windows Deployment Services (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 1809 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 1809 and the Windows PE Addon but it installs the Windows Deployment Services role also. Tip: If you've already downloaded ADK 1809 and the Windows PE Addon and want to save yourself some time, or if you are installing a server offline, copy the contents of a previously downloaded ADK1809+Windows PE Addon 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 3\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. Done ! And that's it for this part, please join me in Part 4 where you'll start configuring and installing SQL Server 2017.
-
Hi, with SCCM only how can I prevent Windows 10 to upgrade to new build 1809 and Office 365 v. 1808 ? I want my Windows 10 remain 1803 and Office 365 v.1808, without block all security patch and minor updates... -
how are you trying to install the SCCM Client agent on the test machine exactly ?
-
I have old deployed SCCM 2012 with too many technical issues. I have deployed a new SCCM server with the following topology: 1. HQ SCCM server (SiteCode UCM) 2. WSUS Server 3. DB Server The three servers are communicating with each other and all things are ok. All servers are windows 2016 and updated. The New SCCM server is 1902 I have a problem in installing the SCCM agent on a test client machine although everything is ok. I reinstalled the DP and MP .. and still has the same issue Please advice
- Earlier
-
SCCM 1902 Folders
delan replied to delan's topic in System Center Configuration Manager (Current Branch)
I've looked with wireshark. I don't understand why the DHCP releas happens? See attached file -
SCCM 1902 Folders
delan replied to delan's topic in System Center Configuration Manager (Current Branch)
Now I see how the folder structure is build. What should be the security rights for the SMSboot folder? Now it is : Group 'SYSTEM' is full control Group 'Administrators' is full control (local) Is this right? -
SCCM 1902 Folders
delan replied to delan's topic in System Center Configuration Manager (Current Branch)
In SMSPXE.log I see : Client Boot TS reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820352" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><TSInfo DeploymentID="00720024" PkgID="00700037" BootImageID="00700033" Architecture="0" Required="1" AlreadyRun="0" ForPXE="1" Disabled="0" PackageAvailable="1" FutureAvailability="0" Expired="0" UEFIArchitectureMismatch="0" ArchitectureMismatch="0"/><TSInfo DeploymentID="00720023" PkgID="00700038" BootImageID="00700034" Architecture="9" Required="1" AlreadyRun="0" ForPXE="1" Disabled="0" PackageAvailable="1" FutureAvailability="0" Expired="0" UEFIArchitectureMismatch="0" ArchitectureMismatch="1"/></ClientIDReply> PXE: 00:15:5D:CA:67:04: Task Sequence deployments: PXE: 00:15:5D:CA:67:04: 00720024, 00700033, 32-bit, required, is valid. (this valid I think) PXE: 00:15:5D:CA:67:04: 00720023, 00700034, 64-bit, required, is not compatible with the 32-bit client. Discarding from list. PXE: 00:15:5D:CA:67:04: Using Task Sequence deployment 00720024.(start using task) Operation: 2, Address type: 1, Address length: 6, Hop Count: 1, Transaction ID: 0467ca5e, Seconds since boot: 1024, Address: 00:15:5d:ca:67:04:00:00:00:00:00:00:00:00:00:00, Host name: , Boot file name: smsboot\00700033\x86\wdsnbp.com, Client IP: 0.0.0.0, Host IP: 0.0.0.0, Server IP: 10.70.202.61, Relay IP: 10.70.202.254 Options: 53, 1: 05 54, 4: 0a 46 ca 3d 97, 17: 00 b3 56 df 6c c3 2c ca 40 87 62 f5 06 c9 b4 1b e2 60, 9: 50 58 45 43 6c 69 65 6e 74 250, 30: 02 01 01 05 04 00 00 00 00 03 02 00 14 04 02 00 ba 06 08 53 43 43 4d 20 50 58 45 0b 01 01 PXE: Sending reply to 10.70.202.254, DHCP. Client Boot TS reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820352" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><TSInfo DeploymentID="00720024" PkgID="00700037" BootImageID="00700033" Architecture="0" Required="1" AlreadyRun="0" ForPXE="1" Disabled="0" PackageAvailable="1" FutureAvailability="0" Expired="0" UEFIArchitectureMismatch="0" ArchitectureMismatch="0"/><TSInfo DeploymentID="00720023" PkgID="00700038" BootImageID="00700034" Architecture="9" Required="1" AlreadyRun="0" ForPXE="1" Disabled="0" PackageAvailable="1" FutureAvailability="0" Expired="0" UEFIArchitectureMismatch="0" ArchitectureMismatch="1"/></ClientIDReply> .... PXE: Sending reply to 10.70.202.203, PXE. (this is client) PXE: Received packet from 10.70.202.203 (DHCP, 00:15:5D:CA:67:02, 10.70.202.61). (=SCCM) Operation: 1, Address type: 1, Address length: 6, Hop Count: 0, Transaction ID: 0467ca5e, Seconds since boot: 0, Address: 00:15:5d:ca:67:04:00:00:00:00:00:00:00:00:00:00, Host name: , Boot file name: , Client IP: 0.0.0.0, Host IP: 0.0.0.0, Server IP: 0.0.0.0, Relay IP: 0.0.0.0 Options: 53, 1: 07 54, 4: 0a 46 ca 3d 97, 17: 00 b3 56 df 6c c3 2c ca 40 87 62 f5 06 c9 b4 1b e2 PXE: : Packet message type is not a discover/solicit or request. Ignoring. (????) -
I've looked to the location and I found this : "C:\Program Files\Microsoft Configuration Manager\bin\X64\SMSBoot\00700033\x86" Can SCCM PXE find this location? Please ...anybody???
-
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 is System Center Configuration Manager (Current Branch) version 1902 as of April the 10th 2019. I blogged how to upgrade to 1902 here. This guide is aimed a new installations of SCCM. Baseline media is used to install new ConfigMgr sites or to upgrade from supported versions, for more information about baseline media please see my blog post here. Note: The SCCM 1902 Current Branch media is not yet available on MSDN or VLSC. When the new baseline media is released I'll update this note. This series is broken down into the following parts:- Part 1 - Get the lab ready, configure ADDS Part 2 - Join CM01 to Domain, add users, create the Systems Management container, delegate permission (This part) 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 - Post configuration 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. Join CM01 to the domain Note: Perform the following on the ConfigMgr server (CM01) as Local Administrator Method #1 - Do it manually To join the domain manually, login to CM01. Start Windows File Explorer. Right-click on This-PC and choose Properties. The System screen will appear. Click on Change settings to the right of Computer name. For the option To rename this computer or change its domain or workgroup, click Change, click Change and for Member of select Domain, enter the Domain details used in Part 1 of this series and then click OK. and enter domain join credentials as appropriate when prompted. Once done you'll get notification that you've joined the domain. Click OK and click Restart Now when prompted. Method #2 - Automate it with PowerShell To join the domain automatically, use the joindomain.ps1 PowerShell script. 1. Copy the script to C:\Scripts on CM01 2. Edit the variables (lines 16-18) as desired before running. 3. Start Windows PowerShell ISE as Administrator and run the script by clicking on the green triangle. Step 2. Add Users to Active Directory Method #1 - Do it manually To create users manually, click on Start and choose Windows Administrative Tools and then select Active Directory Users and Computers. In Active Directory Users and Computers, add new users by expanding <domain name>, select Users and right click, choose New then select User. In the wizard that appears fill in the New Object user details enter the Password details using password P@ssw0rd and click Finish when done. Repeat the above process to add remaining users as appropriate for your environment Testuser, used for testing stuff CM_BA, used for building ConfigMgr created images CM_JD, used for joining computers to the domain CM_RS, used for reporting services. CM_CP, used when installing the Configuration Manager Client for Client Push. CM_NAA, (Network Access Account) used during OSD Note: The PowerShell script creates users and in addition makes a user a local admin on the CM01 server. To facilitate the local administrator creation, you'll need to (optionally) create a GPO manually on AD01 called Allow Inbound File and Printer sharing exception which sets Windows Firewall: Allow inbound file and printer sharing exception to Enabled. To Create the GPO on AD01, click the Start menu and choose Windows Administrative Tools, then select Group Policy Management. Expand Group Policy Objects and Right click, choose New and give it a Name: Allow Inbound File and Printer Sharing Exception. In the GPO settings, expand Computer Configuration, Policies, Administrative Templates, then select Network, Network Connections, Windows Defender Firewall and select the Domain Profile. Locate the Windows Defender Firewall: Allow inbound file and printer sharing exception and set it to Enabled. Apply the changes. After creating the GPO, you'll want to limit it to only apply to your ConfigMgr server (or servers). To do that select the Delegation tab of the GPO, and click on Advanced button. Select the Authenticated Users security group and then scroll down to the Apply Group Policy permission and un-tick the Allow security setting. This denies authenticated users from applying this GPO setting Next, click on the Add button, for Select this object type make sure to select Computers from the Object Types and select the group or Computer object (eg: CM01$) that you want to have this policy apply to. Then select the group (e.g. ConfigMgr Servers) and scroll the permission list until you see the Apply group policy option and then tick the Allow permission. Finally, you need to Link the GPO, to do that, right click on your Domain (in this example it's windowsnoob.lab.local) and select Link an existing GPO. Note: Once the above is completed, please update Group Policy on CM01 using gpupdate /force prior to running the PowerShell script below. Method #2 - Automate it with PowerShell To create users automatically, use the Create Users Usergroups and OUs in AD.ps1 PowerShell script. Tip: You should edit the script and adjust the variables to your liking, for example if you want to change the default password. You may also want to rem out the MDT and MBAM user/groups that are created and change some of the user names within the script. To rem out a line place a # in front of it. 1. Copy the script to C:\scripts on AD01, see the notes above about the GPO creation. 2. Edit the variables [lines 79-100] as desired before running. 3. Start Windows PowerShell ISE as Administrator and run the script by clicking on the green triangle. Step 3. Create the System Management Container Note: Perform the following on the Active Directory Domain Controller server (DC01) as Local Administrator For details of why you are doing this see https://docs.microsoft.com/en-us/sccm/core/plan-design/network/extend-the-active-directory-schema Method #1 - Do it manually Open ADSI Edit, click on Action, then Connect To and click Ok, Double Click on Default Naming Context and the DC= that appears below it. Click on the > and scroll down to CN=System. Right Click on CN=System and choose New, Object choose Container from the options, click Next enter System Management as the value then click Next and then click Finish. The System Management container is created. Click OK and click Restart Now when prompted. Method #2 - Automate it with PowerShell To join the domain automatically, use the Create system management container.ps1 PowerShell script. 1. Copy the script to C:\Scripts on DC01 2. Edit the variables (lines 18-23) as desired before running. 3. Start Windows PowerShell ISE as Administrator and run the script by clicking on the green triangle. Step 4. Delegate Permission Note: Perform the following on the Active Directory Domain Controller server (DC01) as Local Administrator Method #1 - Do it manually Open Active Directory Users and Computers. Click on view, select Advanced Features. Select the System Management Container under System. Right click the System Management container that you just created, choose All Tasks and Delegate Control. When the Welcome to Delegation of Control Wizard appears click next, then click Add. click on Object Types, select Computers. Type in your Configuration Manager server name (CM01) and click on Check Names, it should resolve. Click Ok. Click Next then select Create a Custom Task to Delegate, click Next, make sure This folder, existing objects in this folder and creation of new objects in this folder is selected. Click next, select the 3 permissions General, Property-Specific and Creation-deletion of specific child objects are selected then place a check mark in Full Control. Click Next then click Finish. Tip: Repeat the above process for each site server that you install in a Hierarchy. Method #2 - Automate it with PowerShell To join the domain automatically, use the Delegate Permissions.ps1 PowerShell script. 1. Copy the script to C:\Scripts on DC01 2. Edit the variable (line 24) as desired before running. 3. Start Windows PowerShell ISE as Administrator and run the script by clicking on the green triangle. That's it for this part, please join me in Part 3 where we'll configure the ConfigMgr server with Roles and Features and get Windows ADK and WDS setup.
-
SCCM 1902 Folders
delan replied to delan's topic in System Center Configuration Manager (Current Branch)
Hi Anyweb Thx for response. WDS is not installed anymore. I use PXE responder without WDS In the SMSPXE.log the communication between PXE is working. This is talking to gateway, DHCP, SCCM and client -
SCCM 1902 Folders
anyweb replied to delan's topic in System Center Configuration Manager (Current Branch)
have you verified that the non WDS PXE responder service is started ? -
Hi I have troubles with PXE-boot. My SCCM is version 1902. My DP is setup to answer PXE (without WDS) In my folder' structure I see that SMS_DP$, SMSPKG and SMSPKGC$ are empty In the folder SMSPKGSIG a lot of .tar files and a lot of folders (ID's with versionnumbers) In folder SMSSIG$ only .tar files Is this right?? Or where are the bootstartup files should be located? Thx Best Regards Delan
-
I see "Boot file name: smsboot\0070002F\x86\wdsnbp.com" Where is this precisely located in the folder structure???? c:\Program Files\Microsoft Configuration Manager\..........????????????
-
Surely someone knew the answer. Oh well. Re-arranged a few parts of the task that had to be done online, and used the source switch in the configmgr install options to point to the package location. It works. -
Hi My SCCM = 1902 (in VM - Hyper-V) = 10.70.202.61 My pfsense is not VM = gateway 10.70.202.254 (with ip helper 10.70.202.11 (to DHCP) and Helper to 10.70.202.61 = SCCM) Client (VM-Hyper-V with Legacy NIC) In DP bootimage x86 (0070002F) and x64 (00700030), operating system (00700012) , client package (00700002) The task sequence (00700032) = deploy on unknown computers I've tried many thing as renew the boot images, client i a known collection... What happens.... When I startup th client (00:15:5D:CA:67:04) he get notting. After ten minutes I see the IP-adres but also PXE-E55 (see attached file) When I look to smspxe.log , I see many thing that Iknow but I don't see whats wrong : (in bold some comment) PXE: Received packet from 0.0.0.0 (DHCP, 00:15:5D:CA:67:02, 10.70.202.61). (startup at 11:16:42) Operation: 1, Address type: 1, Address length: 6, Hop Count: 0, Transaction ID: 0467ca5e, Seconds since boot: 1024, Address: 00:15:5d:ca:67:04:00:00:00:00:00:00:00:00:00:00, Host name: , Boot file name: , Client IP: 0.0.0.0, Host IP: 0.0.0.0, Server IP: 0.0.0.0, Relay IP: 0.0.0.0 Options: 53, 1: 01 55, 24: 01 02 03 05 06 0b 0c 0d 0f 10 11 12 2b 36 3c 43 80 81 82 83 84 85 86 87 57, 2: 04 ec 97, 17: 00 b3 56 df 6c c3 2c ca 40 87 62 f5 06 c9 b4 1b e2 93, 2: 00 00 94, 3: 01 02 01 60, 32: 50 58 45 43 6c 69 65 6e 74 3a 41 72 63 68 3a 30 30 30 30 30 3a 55 4e 44 49 3a 30 30 32 30 30 31 PXE: Received packet from 10.70.202.254 (DHCP, 00:15:5D:CA:67:02, 10.70.202.61). (gateway - sccm from ip helper?) Operation: 1, Address type: 1, Address length: 6, Hop Count: 1, Transaction ID: 0467ca5e, Seconds since boot: 1024, Address: 00:15:5d:ca:67:04:00:00:00:00:00:00:00:00:00:00, Host name: , Boot file name: , Client IP: 0.0.0.0, Host IP: 0.0.0.0, Server IP: 0.0.0.0, Relay IP: 10.70.202.254 Options: 53, 1: 01 55, 24: 01 02 03 05 06 0b 0c 0d 0f 10 11 12 2b 36 3c 43 80 81 82 83 84 85 86 87 57, 2: 04 ec 97, 17: 00 b3 56 df 6c c3 2c ca 40 87 62 f5 06 c9 b4 1b e2 93, 2: 00 00 94, 3: 01 02 01 60, 32: 50 58 45 43 6c 69 65 6e 74 3a 41 72 63 68 3a 30 30 30 30 30 3a 55 4e 44 49 3a 30 30 32 30 30 31 PXE: 00:15:5D:CA:67:04: Operation=1, MessageType=1, Architecture=0, Continuation=0 (arch=0? 32bit why ... 04=client) PXE: 00:15:5D:CA:67:04: Parsed a discover/solicit packet. PXE: 00:15:5D:CA:67:04: 6CDF56B3-2CC3-40CA-8762-F506C9B41BE2: Client is 32-bit, BIOS, Firmware. PXE: 00:15:5D:CA:67:04: Operation=1, MessageType=1, Architecture=0, Continuation=0 PXE: 00:15:5D:CA:67:04: Parsed a discover/solicit packet. PXE: 00:15:5D:CA:67:04: 6CDF56B3-2CC3-40CA-8762-F506C9B41BE2: Client is 32-bit, BIOS, Firmware. (why 2 times?) PXE: 00:15:5D:CA:67:04: Prioritizing local MP http://SCCM.test.local. (he know the MP)(11:16:43) Not in SSL (not secured) PXE: 00:15:5D:CA:67:04: Prioritizing local MP http://SCCM.test.local. (why another time) Not in SSL Not in SSL Not in SSL Client Boot Get ID Info reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><ClientIDInfo ItemKey="0" ClientID="" DuplicateSMBIOS="0" DuplicateMACAddress="0" MatchType="0"/></ClientIDReply> PXE: 00:15:5D:CA:67:04: System records: PXE: 00:15:5D:CA:67:04: 0, , SMBIOS ID is NOT a match, MAC Address is NOT a match. PXE: 00:15:5D:CA:67:04: No valid system records. (no such machine in DB) Operation: 2, Address type: 1, Address length: 6, Hop Count: 0, Transaction ID: 0467ca5e, Seconds since boot: 1024, Address: 00:15:5d:ca:67:04:00:00:00:00:00:00:00:00:00:00, Host name: , Boot file name: , Client IP: 0.0.0.0, Host IP: 0.0.0.0, Server IP: 10.70.202.61, Relay IP: 0.0.0.0 Options: 53, 1: 02 54, 4: 0a 46 ca 3d 97, 17: 00 b3 56 df 6c c3 2c ca 40 87 62 f5 06 c9 b4 1b e2 60, 9: 50 58 45 43 6c 69 65 6e 74 PXE: Sending reply to 255.255.255.255, DHCP. (broadcast?) Client Boot Get ID Info reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><ClientIDInfo ItemKey="0" ClientID="" DuplicateSMBIOS="0" DuplicateMACAddress="0" MatchType="0"/></ClientIDReply> PXE: 00:15:5D:CA:67:04: System records: PXE: 00:15:5D:CA:67:04: 0, , SMBIOS ID is NOT a match, MAC Address is NOT a match. PXE: 00:15:5D:CA:67:04: No valid system records. Operation: 2, Address type: 1, Address length: 6, Hop Count: 1, Transaction ID: 0467ca5e, Seconds since boot: 1024, Address: 00:15:5d:ca:67:04:00:00:00:00:00:00:00:00:00:00, Host name: , Boot file name: , Client IP: 0.0.0.0, Host IP: 0.0.0.0, Server IP: 10.70.202.61, Relay IP: 10.70.202.254 Options: 53, 1: 02 54, 4: 0a 46 ca 3d 97, 17: 00 b3 56 df 6c c3 2c ca 40 87 62 f5 06 c9 b4 1b e2 60, 9: 50 58 45 43 6c 69 65 6e 74 PXE: Sending reply to 10.70.202.254, DHCP. (11:16:43) PXE: Received packet from 0.0.0.0 (DHCP, 00:15:5D:CA:67:02, 10.70.202.61).(11:16:46) Operation: 1, Address type: 1, Address length: 6, Hop Count: 0, Transaction ID: 0467ca5e, Seconds since boot: 1024, Address: 00:15:5d:ca:67:04:00:00:00:00:00:00:00:00:00:00, Host name: , Boot file name: , Client IP: 0.0.0.0, Host IP: 0.0.0.0, Server IP: 0.0.0.0, Relay IP: 0.0.0.0 Options: 53, 1: 03 50, 4: 0a 46 ca cb 55, 24: 01 02 03 05 06 0b 0c 0d 0f 10 11 12 2b 36 3c 43 80 81 82 83 84 85 86 87 57, 2: 04 ec 54, 4: 0a 46 ca 0b 97, 17: 00 b3 56 df 6c c3 2c ca 40 87 62 f5 06 c9 b4 1b e2 93, 2: 00 00 94, 3: 01 02 01 60, 32: 50 58 45 43 6c 69 65 6e 74 3a 41 72 63 68 3a 30 30 30 30 30 3a 55 4e 44 49 3a 30 30 32 30 30 31 PXE: Received packet from 10.70.202.254 (DHCP, 00:15:5D:CA:67:02, 10.70.202.61). Operation: 1, Address type: 1, Address length: 6, Hop Count: 1, Transaction ID: 0467ca5e, Seconds since boot: 1024, Address: 00:15:5d:ca:67:04:00:00:00:00:00:00:00:00:00:00, Host name: , Boot file name: , Client IP: 0.0.0.0, Host IP: 0.0.0.0, Server IP: 0.0.0.0, Relay IP: 10.70.202.254 Options: 53, 1: 03 50, 4: 0a 46 ca cb 55, 24: 01 02 03 05 06 0b 0c 0d 0f 10 11 12 2b 36 3c 43 80 81 82 83 84 85 86 87 57, 2: 04 ec 54, 4: 0a 46 ca 0b 97, 17: 00 b3 56 df 6c c3 2c ca 40 87 62 f5 06 c9 b4 1b e2 93, 2: 00 00 94, 3: 01 02 01 60, 32: 50 58 45 43 6c 69 65 6e 74 3a 41 72 63 68 3a 30 30 30 30 30 3a 55 4e 44 49 3a 30 30 32 30 30 31 PXE: Received packet from 10.70.202.203 (PXE, 00:15:5D:CA:67:02, 10.70.202.61).(get answer from client) PXE: 00:15:5D:CA:67:04: Operation=1, MessageType=3, Architecture=0, Continuation=0 PXE: 00:15:5D:CA:67:04: Parsed a request packet. PXE: 00:15:5D:CA:67:04: 6CDF56B3-2CC3-40CA-8762-F506C9B41BE2: Client is 32-bit, BIOS, Firmware. Operation: 1, Address type: 1, Address length: 6, Hop Count: 0, Transaction ID: 0467ca5e, Seconds since boot: 1024, Address: 00:15:5d:ca:67:04:00:00:00:00:00:00:00:00:00:00, Host name: , Boot file name: , Client IP: 10.70.202.203, Host IP: 0.0.0.0, Server IP: 0.0.0.0, Relay IP: 0.0.0.0 Options: 53, 1: 03 55, 24: 01 02 03 05 06 0b 0c 0d 0f 10 11 12 2b 36 3c 43 80 81 82 83 84 85 86 87 57, 2: 04 ec 97, 17: 00 b3 56 df 6c c3 2c ca 40 87 62 f5 06 c9 b4 1b e2 93, 2: 00 00 94, 3: 01 02 01 60, 32: 50 58 45 43 6c 69 65 6e 74 3a 41 72 63 68 3a 30 30 30 30 30 3a 55 4e 44 49 3a 30 30 32 30 30 31 PXE: 00:15:5D:CA:67:04: Operation=1, MessageType=3, Architecture=0, Continuation=0 PXE: 00:15:5D:CA:67:04: Parsed a request packet. PXE: 00:15:5D:CA:67:04: 6CDF56B3-2CC3-40CA-8762-F506C9B41BE2: Client is 32-bit, BIOS, Firmware. PXE: 00:15:5D:CA:67:04: Prioritizing local MP http://SCCM.test.local PXE: 00:15:5D:CA:67:04: Operation=1, MessageType=3, Architecture=0, Continuation=0 PXE: 00:15:5D:CA:67:04: Parsed a request packet. PXE: 00:15:5D:CA:67:04: 6CDF56B3-2CC3-40CA-8762-F506C9B41BE2: Client is 32-bit, BIOS, Firmware. Not in SSL PXE: 00:15:5D:CA:67:04: Prioritizing local MP http://SCCM.test.local PXE: 00:15:5D:CA:67:04: Prioritizing local MP http://SCCM.test.local Not in SSL Not in SSL Not in SSL Not in SSL Client Boot Get ID Info reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><ClientIDInfo ItemKey="0" ClientID="" DuplicateSMBIOS="0" DuplicateMACAddress="0" MatchType="0"/></ClientIDReply>(11:16:47) PXE: 00:15:5D:CA:67:04: System records: PXE: 00:15:5D:CA:67:04: 0, , SMBIOS ID is NOT a match, MAC Address is NOT a match. PXE: 00:15:5D:CA:67:04: No valid system records. (another time no match in DB) Not in SSL Client Boot Get ID Info reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><ClientIDInfo ItemKey="0" ClientID="" DuplicateSMBIOS="0" DuplicateMACAddress="0" MatchType="0"/></ClientIDReply> PXE: 00:15:5D:CA:67:04: Prioritizing local MP http://SCCM.test.local PXE: 00:15:5D:CA:67:04: System records: PXE: 00:15:5D:CA:67:04: 0, , SMBIOS ID is NOT a match, MAC Address is NOT a match. PXE: 00:15:5D:CA:67:04: No valid system records. Not in SSL PXE: 00:15:5D:CA:67:04: Prioritizing local MP http://SCCM.test.local Not in SSL Not in SSL Not in SSL Client Boot Get ID Info reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><ClientIDInfo ItemKey="0" ClientID="" DuplicateSMBIOS="0" DuplicateMACAddress="0" MatchType="0"/></ClientIDReply> PXE: 00:15:5D:CA:67:04: System records: PXE: 00:15:5D:CA:67:04: 0, , SMBIOS ID is NOT a match, MAC Address is NOT a match. PXE: 00:15:5D:CA:67:04: No valid system records. PXE: 00:15:5D:CA:67:04: Prioritizing local MP http://SCCM.test.local Client Boot TS reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820352" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><TSInfo DeploymentID="00720022" PkgID="00700032" BootImageID="0070002F" Architecture="0" Required="1" AlreadyRun="0" ForPXE="1" Disabled="0" PackageAvailable="1" FutureAvailability="0" Expired="0" UEFIArchitectureMismatch="0" ArchitectureMismatch="0"/></ClientIDReply> (first time the TS) PXE: 00:15:5D:CA:67:04: Task Sequence deployments: PXE: 00:15:5D:CA:67:04: 00720022, 0070002F, 32-bit, required, is valid. (ok Ithink) PXE: 00:15:5D:CA:67:04: Using Task Sequence deployment 00720022. Operation: 2, Address type: 1, Address length: 6, Hop Count: 0, Transaction ID: 0467ca5e, Seconds since boot: 1024, Address: 00:15:5d:ca:67:04:00:00:00:00:00:00:00:00:00:00, Host name: , Boot file name: smsboot\0070002F\x86\wdsnbp.com, Client IP: 0.0.0.0, Host IP: 0.0.0.0, Server IP: 10.70.202.61, Relay IP: 0.0.0.0 Options: 53, 1: 05 54, 4: 0a 46 ca 3d 97, 17: 00 b3 56 df 6c c3 2c ca 40 87 62 f5 06 c9 b4 1b e2 60, 9: 50 58 45 43 6c 69 65 6e 74 250, 30: 02 01 01 05 04 00 00 00 00 03 02 00 14 04 02 00 ba 06 08 53 43 43 4d 20 50 58 45 0b 01 01 PXE: Sending reply to 255.255.255.255, DHCP. Client Boot TS reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820352" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><TSInfo DeploymentID="00720022" PkgID="00700032" BootImageID="0070002F" Architecture="0" Required="1" AlreadyRun="0" ForPXE="1" Disabled="0" PackageAvailable="1" FutureAvailability="0" Expired="0" UEFIArchitectureMismatch="0" ArchitectureMismatch="0"/></ClientIDReply> PXE: 00:15:5D:CA:67:04: Task Sequence deployments: PXE: 00:15:5D:CA:67:04: 00720022, 0070002F, 32-bit, required, is valid. PXE: 00:15:5D:CA:67:04: Using Task Sequence deployment 00720022. Operation: 2, Address type: 1, Address length: 6, Hop Count: 1, Transaction ID: 0467ca5e, Seconds since boot: 1024, Address: 00:15:5d:ca:67:04:00:00:00:00:00:00:00:00:00:00, Host name: , Boot file name: smsboot\0070002F\x86\wdsnbp.com, Client IP: 0.0.0.0, Host IP: 0.0.0.0, Server IP: 10.70.202.61, Relay IP: 10.70.202.254 Options: 53, 1: 05 54, 4: 0a 46 ca 3d 97, 17: 00 b3 56 df 6c c3 2c ca 40 87 62 f5 06 c9 b4 1b e2 60, 9: 50 58 45 43 6c 69 65 6e 74 250, 30: 02 01 01 05 04 00 00 00 00 03 02 00 14 04 02 00 ba 06 08 53 43 43 4d 20 50 58 45 0b 01 01 PXE: Sending reply to 10.70.202.254, DHCP. Not in SSL Not in SSL Client Boot TS reply: <ClientIDReply><Identification Unknown="0" DuplicateSMBIOS="0" DuplicateMACAddress="0" ItemKey="2046820352" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><TSInfo DeploymentID="00720022" PkgID="00700032" BootImageID="0070002F" Architecture="0" Required="1" AlreadyRun="0" ForPXE="1" Disabled="0" PackageAvailable="1" FutureAvailability="0" Expired="0" UEFIArchitectureMismatch="0" ArchitectureMismatch="0"/></ClientIDReply> PXE: 00:15:5D:CA:67:04: Task Sequence deployments: PXE: 00:15:5D:CA:67:04: 00720022, 0070002F, 32-bit, required, is valid. PXE: 00:15:5D:CA:67:04: Using Task Sequence deployment 00720022. Operation: 2, Address type: 1, Address length: 6, Hop Count: 0, Transaction ID: 0467ca5e, Seconds since boot: 1024, Address: 00:15:5d:ca:67:04:00:00:00:00:00:00:00:00:00:00, Host name: , Boot file name: smsboot\0070002F\x86\wdsnbp.com, Client IP: 10.70.202.203, Host IP: 0.0.0.0, Server IP: 10.70.202.61, Relay IP: 0.0.0.0 Options: 53, 1: 05 54, 4: 0a 46 ca 3d 97, 17: 00 b3 56 df 6c c3 2c ca 40 87 62 f5 06 c9 b4 1b e2 60, 9: 50 58 45 43 6c 69 65 6e 74 250, 30: 02 01 01 05 04 00 00 00 00 03 02 00 14 04 02 00 ba 06 08 53 43 43 4d 20 50 58 45 0b 01 01 PXE: Sending reply to 10.70.202.203, PXE. (11:16:47) PXE: Received packet from 10.70.202.203 (DHCP, 00:15:5D:CA:67:02, 10.70.202.61). (11:16:54) Operation: 1, Address type: 1, Address length: 6, Hop Count: 0, Transaction ID: 0467ca5e, Seconds since boot: 0, Address: 00:15:5d:ca:67:04:00:00:00:00:00:00:00:00:00:00, Host name: , Boot file name: , Client IP: 0.0.0.0, Host IP: 0.0.0.0, Server IP: 0.0.0.0, Relay IP: 0.0.0.0 Options: 53, 1: 07 54, 4: 0a 46 ca 3d 97, 17: 00 b3 56 df 6c c3 2c ca 40 87 62 f5 06 c9 b4 1b e2 PXE: Received packet from 0.0.0.0 (DHCP, 00:15:5D:CA:67:02, 10.70.202.61). PXE: : Packet message type is not a discover/solicit or request. Ignoring. (???????) Operation: 1, Address type: 1, Address length: 6, Hop Count: 0, Transaction ID: 0467ca5e, Seconds since boot: 1024, Address: 00:15:5d:ca:67:04:00:00:00:00:00:00:00:00:00:00, Host name: , Boot file name: , Client IP: 0.0.0.0, Host IP: 0.0.0.0, Server IP: 0.0.0.0, Relay IP: 0.0.0.0 Options: 53, 1: 03 50, 4: 0a 46 ca cb 55, 24: 01 02 03 05 06 0b 0c 0d 0f 10 11 12 2b 36 3c 43 80 81 82 83 84 85 86 87 57, 2: 04 ec 54, 4: 0a 46 ca 0b 97, 17: 00 b3 56 df 6c c3 2c ca 40 87 62 f5 06 c9 b4 1b e2 93, 2: 00 00 94, 3: 01 02 01 60, 32: 50 58 45 43 6c 69 65 6e 74 3a 41 72 63 68 3a 30 30 30 30 30 3a 55 4e 44 49 3a 30 30 32 30 30 31 PXE: Received packet from 10.70.202.254 (DHCP, 00:15:5D:CA:67:02, 10.70.202.61). PXE: 00:15:5D:CA:67:04: Operation=1, MessageType=3, Architecture=0, Continuation=0 PXE: 00:15:5D:CA:67:04: Parsed a request packet. .... Thanks for your time Best Regards Delan
-
Hello, I have to use a vbs script to update windows drivers (it's an old script with lots of reminiscences that I'm migrating to sccm later). So I use a task sequence to do the job. When I migrate windows 7 to windows 10, the vbs works perfectly because it is in this mode: https://ibb.co/1LtMyCC When I make a windows 10 build update, the driver update starts in another phase (while it is in the same place in the task sequence): https://ibb.co/Pxv59qC in this phase all the drivers do not install well! Is there a way to wait for the OS to finish booting before running the drivers. Thansk for your help (and sorry for my bad english ;-))
