Jump to content


All Activity

This stream auto-updates     

  1. Today
  2. There is a user voice for it, I would not hold my breath that it will happen anytime soon. As it only has 0 votes. https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/40878685-hardware-inventory-to-collect-certificates
  3. When the application starts it evaluates the detection (presence) of your dependency apps. Maybe you need to add an extra detection method on your dependency app to skip installation of the new C++ when a certain version is found OR create in your installation program an uninstall first of the previous version.
  4. thanks - hope Microsoft will include in the future .
  5. Yesterday
  6. Introduction These are my notes from a session shown today @ Microsoft Ignite 2020, the session was hosted by Steve Dispensa (Director of Program Management at Microsoft Endpoint Manager) and Ramya Chitrakar (Director of Engineering at Microsoft Endpoint Manager). For the last couple of years at Ignite I blog my notes for sessions I'm interested in as I always find it nice to later refer to this reading material and punctuate it with content I've covered, and sometimes the videos just flow by too fast and you miss out on important points. Where appropriate I'll link to content that I've covered that is referred to in the video. Agenda This is part 1 of a two part session and below is the agenda. MEM and the new normal What's new in Microsoft Endpoint Manager Demos Takeaways and next steps MEM and the new normal A year ago we all started our day in the usual way, grabbing coffee, going to the office, and interacting directly with our fellow colleagues but Covid 19 changed that very quickly as businesses shut their doors all around the world. I know this myself as I've been working from home since mid-March this year and as a direct result of that I upgraded my home office to make the work environment more appealing. Now many of us are working from home either full time or most of the time, and that involves changes in how we access and use company resources. We are working across more devices, more scenarios and often without the traditional safety net of onsite support or help desks that you can visit directly for assistance. This rapid change has guaranteed one thing, all businesses must have a remote working plan that lets employees work with 100% productivity from home. "Businesses need users to be fully effective when working remotely and need to be able to switch between remote work and office work without missing a beat" Last year at Ignite Microsoft released Microsoft Endpoint Manager, the integrated solution between all the endpoints in your estate. MEM brings together Intune (intelligent cloud) for all of your cloud attached endpoints, Configuration Manager (Intelligent Edge) for all your on-premises endpoints and other endpoint management tools suchs as Windows Autopilot, Desktop Analytics and Proactive Remediations to bring the power of the cloud to your whole enterprise. Microsoft have seen exponential growth in cloud attachment in the last year. "Massive customer adoption" MEM brings together the most comprehensive set of endpoint management capabilities in the industry. Starting with security it integrates with the most sophisticated solutions in the market and lets you establish baselines and implement policy for your users and devices. Risk based controls like Conditional Access lets you make sure that your endpoints are secure and compliant before gaining access to sensitive company resources. Unified management has deep integration with Microsoft 365 apps and the new Microsoft Edge. Zero touch provisioning works across different platforms to deliver unprecedented efficiency for IT Pros. And of course there is advanced analytics with Desktop Analytics, Log Analytics, real time advanced threat detection and more, and of course it's all deeply integrated with Microsoft 365 and can utilize RBAC (role based access control), Microsoft Graph (to automate tasks), PowerShell, auditing and cloud content optimization. So how does it all fit together ? "Tenant attach" Microsoft's goal is to bring the power of the cloud to your whole enterprise. Microsoft released tenant attach which allows you to have an easy and low risk path to cloud attached Configuration Manager to start gaining cloud benefits. I blogged about tenant attach when it was first released in Endpoint Manager technical preview below: Enabling tenant attach Utilizing tenant attach Organizations can also use co-management to manage Windows 10 using both Config Manager and Intune at the same time, this capability is unique in the industry. New customers can go directly to the cloud with Intune or migrate over time with co-management of Config Manager and Intune. Below you can see the increase in numbers of Windows 10 devices managed in the cloud (Intune) in the last year. The target for next year is 35% managed by Intune and by 2022 they are forecasting 50% of Windows 10 devices will be cloud attached. Nobody had it easy through this crisis, but customers that had modern management definitely had a smoother run. The pandemic drove permanent changes in the way modern workplaces worked, customers deployed CMG's, VPN usage went crazy. At this point however most customers have made it through the initial problems and are focusing on rebuilding for the future. So let's focus on the new capabilities in Microsoft Endpoint Manager. What's new MEM will support virtual endpoints so you can support Windows Virtual Desktop and later this year, third party VDI right alongside your physical pc's. They will preview this capability later in the year. Customers want to manage all their endpoints with MEM and Microsoft have a first class management experience of MacOS. New capabilities there as well including the ability to deploy scripts to devices, new enrollment experiences that utilize Single Sign-on improvements across applications and new managed life-cycle features. Shared iPad for Business support. Will let customers deploy shared iPads to users, login with their Azure AD work accounts in separate partitions on the device including having each user having a separate device passcode on the device. Introducing Microsoft Tunnel. Customers have been asking for this literally for years. Tunnel allows you to connect your users on iOS and Android to apps and services. Full device and per app VPN with split tunneling. Natively integrated with Microsoft 365 and Conditional Access so you can protect your sensitive company resources. This is now available in preview to a broad audience over the next couple of days. Please check it out. "Zero Trust" Cloud attached management is critical to Zero Trust Security and Endpoints are trusted only when identity is securely established. MEM si growing fast, and it also offers the following areas of investment in new classes of shared devices. Today Microsoft will announce the general availability of Endpoint Analytics which is one of the fastest growing new capabilities in MEM. Every cloud attachment is unique and there are several different on-ramps to cloud management and (according to Microsoft) it's just a couple of clicks, but in reality you do have to satisfy prerequisites and those take some time to setup prior to those clicks. Demos As Steve already mentioned there's been a massive shift towards remote work and a strong indication that this trend will continue even in the long term. Ensuring business continuity and resilience is going to be key for IT. Microsoft Productivity score and Endpoint Analytics enable the IT Pro to understand how organizations are working, how technology is supporting them and how productive their end users are. "Microsoft Productivity score and Endpoint Analytics enable the IT Pro to understand how organizations are working, how technology is supporting them and how productive their end users are." Analytics really makes the IT Pro the hero. Endpoint Analytics is release to general availability at Ignite, Microsoft Productivity Score will be released in October. Below you can see the productivity score and how it displays employee experience and technology experience. Endpoint analytics is part of Technology experience, last year Microsoft announced some cool new features in that area to measure startup performance. It also offers Proactive remediations, recommended software and application health reports. Application health (new) is based on the 0-100 paradigm. Shows you top applications that affect your performance over the last 14 days. Overlays crash data over the usage of each app and the number of devices that are using this app. This let's you focus on the top applications that are impacting productivity. Conditional access Conditional access enables zero trust access control where identity is the parameter and all endpoints are treated equally regardless of the network that they attach to. Customers are telling Microsoft that they have some legacy applications that are simply not ready for modern authentication and conditional access. "Microsoft Tunnel is a mobile access gateway. Microsoft Tunnel is a vpn gateway to allow your iOS and Android users to access apps and on premise resources using modern authentication, single sign-on (sso) and conditional access." Microsoft Tunnel is a mobile access gateway to take care of this. Microsoft Tunnel is a vpn gateway to allow your iOS and Android users to access apps and on premise resources using modern authentication, single sign-on (sso) and conditional access. This is setup by the IT admin. There are three main steps. Configure the gateway Deploy VPN profile for Tunnel Deploy Edge and Tunnel apps for these devices You can find this new functionality under Tenant Administration in the Endpoint Manager console. Key takeaways Recommended reading Working from home - the new reality Introducing Microsoft Tunnel Microsoft Productivity Score https://adoption.microsoft.com/productivity-score/ Endpoint Analytics https://docs.microsoft.com/en-us/mem/analytics/overview Microsoft Endpoint Manager https://endpoint.microsoft.com
  7. ok i've connected to your lab just now and fixed the internal issues, basically to summarize your internal lab was not following my lab setup, and you had DNS configured incorrectly, so your srv0001 server (dc01) was 192.168.3.1 or something, when it should have been 192.168.11.101 and so on, so when i pinged from the sccm server to the dc it replied back with 192.168.3.1 (or whatever ip it was, i forget), in addition, your webserver had ip address of 192.168.11.100 so it was not going to work, ive fixed dns by deleting the stale entries, and manually configuring the ip on the dc and on the sccm server and lastly disabled ipv6 on all 3 servers, rebooted them, and verified all could ping each other, that's the first thing you need to have working before trying anything else, don't reuse labs from something else, they will break, always build labs from scratch as per the offered guide, then it will work 100% lastly, i confirmed that your smoothwall was configured correctly, it looked ok, then i checked port 80 on your internet ip address with canyouseeme.org and it didn't work, that means that more than likely your internet provider or router/adsl/whatever is blocking port 80, so please check that
  8. Since Certs are not inventory by ConfigMgr, you will not be able to query on cert templates either.
  9. thank you is there a way to create a query base on certificate template ?
  10. Hi, We have this behavior when upgrading the Config Manager client and i'm just curious if someone recognizes it and dealt with it before. This is what happens; After a Client upgrade of the Config Manager client to 1910 some desktops fall into sleep mode, they shouldn't because their powersettings are set with Collection based power scheme. If you reboot the device everthing works again. With the upgrade to 1810 i noticed something similiar, client temporary unaware of settings, with surpressed reboots for workstations on the Deployment of Software Updates. These devices had pending reboots and rebooted directly after the upgrade of the client. It was not supressed at that time. The upgrade of the client is done via the build in Pre-production Client Deployment collection. I'm now thinking of another approach next time. Create a custom deployment of the CCM client with triggered communication between client and server. But you'd expect this as something default... Is there a way to prevent this?
  11. There are no built in inventory task for Certs and therefore no reports for this either.
  12. hi is there a way to find/display specific certificate that is on client side is there and rdl for the sccm report server ? can i see the certificate in resource explorer ? roni
  13. Last week
  14. Thank you. Personally, I can't see anything of note in those logs. The only relevant clue is in Windows application logs, which record the installer's executable crashing: Exception code 0xc0000005 is a memory violation, and the exit code in AppEnforce (3221225477) seems to mean the same thing. I'll speak to the developers, but it's just strange how this only happens when triggered automatically. All these logs are from a VM with Windows 10 1909, and no software installed. The only antivirus is Windows Defender, which I disabled by local Group Policy. AppLogs.zip
  15. Hi. What does your Format and Partition Disk task sequence step look like?
  16. Hi everyone, Hope all are being safe and sound !! Need someone experience in setting up ip helpers for pxe boot as we are trying to establish the same in our environment but having some issues. Since we have our VLAN ranges and WDS server on different subnet and due to cost constraints we can’t set up a local WDS for this range we thought about going for up helpers for it . It’s already configured on switched by our network team but need someone expertise with the below : > after adding the vlan scope in our DHCP server do we still need to keep option 66 and 67 enabled or disable?? > if we implement ip helper from network side and keep the option 66 and 67 enabled at DHCP would it mess with the functionality?? Is it mandatory to get them disable?? > what are the changes we should be doing at DHCP side for this pxe boot using ip helper? Regards Shashi Dubey
  17. ok well if you can zip up all logs starting with app*.log in your c:\windows\ccm\logs folder and attach them here i can take a look
  18. Thanks for your reply. There's nothing documented, to say that the application requires a user to be logged-on, but I thought SCCM always used the system account, anyway. In both scenarios, the installer's temporary files and logs appear in C:\Windows\Temp, as opposed to the user's %Temp% folder, which is the bahaviour of the system account. Either way, I always test my deployments using PSExec to run the installer in the system context, and that always works, with this application. Also, the installation fails whether a user is logged-on or not, I'm afraid. So I don't know where that leaves us. Thanks.
  19. I am using SCCM current branch and a month ago before upgrade images were applying just fine. No I get errors when applying operating system. I have done all kinds of searching and cannot find an answer. Below is partial log with error. System root for target OS is C:\WINDOWS, System drive is C: ApplyOperatingSystem 9/16/2020 5:22:48 PM 1748 (0x06D4) OSArchitecture=X64 ApplyOperatingSystem 9/16/2020 5:22:48 PM 1748 (0x06D4) OS version is 10.0 ( OS system file version found to be 10.0.18362.1 ) ApplyOperatingSystem 9/16/2020 5:22:48 PM 1748 (0x06D4) Successfully loaded a source BCD boot system ApplyOperatingSystem 9/16/2020 5:22:48 PM 1748 (0x06D4) SetupNewOS: Loaded source boot system from target volume "C:\" ApplyOperatingSystem 9/16/2020 5:22:48 PM 1748 (0x06D4) !sBootDevicePath.empty(), HRESULT=80004005 (..\bootvolume.cpp,34) ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) System partition not set ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) Unable to find the partition that contains the OS boot loaders. Please ensure the hard disks have been properly partitioned Unspecified error (Error: 80004005; Source: Windows) ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) Command line for extension .exe is "%1" %* ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) Set command line: "bcdboot.exe" C:\WINDOWS /l en-US ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) Executing command line: "bcdboot.exe" C:\WINDOWS /l en-US with options (0, 4) ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) Process completed with exit code 15250 ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) uExitCode == 0, HRESULT=80004005 (..\bcdbooter.cpp,88) ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) Bcdboot failed! bcdboot.exe C:\WINDOWS /l en-US failed (15250) stdout: Failure when attempting to copy boot files. stderr: ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) TS::Boot::BcdBooter::InstallBootFilesAndConfigBCD (sTargetSystemRoot, this->defaultLanguage, sBootVolume), HRESULT=80004005 (installimage.cpp,1132) ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) Unloading offline SOFTWARE registry hive ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) Unloading offline SYSTEM registry hive ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) SetupNewOs(&pBootSystem), HRESULT=80004005 (installimage.cpp,1943) ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) Configure(), HRESULT=80004005 (installimage.cpp,2121) ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) Installation of image 1 in package FC10001B failed to complete.. Unspecified error (Error: 80004005; Source: Windows) ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) installer.install(), HRESULT=80004005 (installimage.cpp,2187) ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) Closing image file C:\_SMSTaskSequence\Packages\FC10001B\Win10_1903_Reg.wim ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) ReleaseSource() for C:\_SMSTaskSequence\Packages\FC10001B. ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) reference count 1 for the source C:\_SMSTaskSequence\Packages\FC10001B before releasing ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) Released the resolved source C:\_SMSTaskSequence\Packages\FC10001B ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) InstallImage( g_InstallPackageID, g_ImageIndex, targetVolume, ImageType_OS, g_ConfigPackageID, g_ConfigFileName, bOEMMedia, g_RunFromNet ), HRESULT=80004005 (applyos.cpp,513) ApplyOperatingSystem 9/16/2020 5:22:54 PM 1748 (0x06D4) Process completed with exit code 2147500037 TSManager 9/16/2020 5:22:54 PM 1032 (0x0408)
  20. the difference (based on what you said) is that one of those two installations may have been in user context, as in the user clicked and ran the installer, so is your software dependent on a user being logged on ?
  21. Hi. I have an application which has a "required" deployment. If I leave it to install by itself, it always fails. But if I log-on to one of the target computers, open Software Center, go into the deployment and click "Install", it always works. So what I'm wondering is: when SCCM automatically triggers the deployment, how is that different to triggering it from Software Center? Why would one work, but not the other? I suspect the problem is to do with the executable itslelf, but understanding the mechanics of how the two scenarios differ, could help me test and troubleshoot the issue. I hope someone can shed some light! Thanks.
  22. Earlier
  23. Trying to add the driver to existing package, it does not option to select the existing driver package. Where can I check the error log and resolve this issue? Here is the good one below and able to pick the driver package Does anyone face this issue before? Thanks
  24. I'm trying to deploy an application that has multiple dependencies. One of the dependencies is Visual C. The application deployment fails because it states that Visual C already exists and it must be uninstalled through control panel for the deployment to succeed. Is there a way during application deployment to bypass a dependency if it already exists on the target computer? Thanks in advance.
  25. There is always Powershell ... Import-Module -Name "$(split-path $Env:SMS_ADMIN_UI_PATH)\ConfigurationManager.psd1" $SiteCode = Get-PSDrive -PSProvider CMSITE Set-Location "$($SiteCode.Name):" #################################### $server = 'sccm01' # MECM Primary Server Name $role1 = 'Company Resource Access Manager' # Security Role Name $role2 = 'Compliance Settings Manager' # Security Role Name $DiffOnly = $false # change to $true to show differences only #################################### $ns = 'root\SMS\Site_'+$SiteCode function _getRoles{ Param( [parameter(position=0)] [string] $role ) $props = (Get-CMSecurityRole -Name $role -ErrorAction SilentlyContinue | Select *).Properties $rules = [System.Collections.Generic.List[psobject]]::new() $props.Operations | ForEach-Object { $ops = $_.GrantedOperations $typeId = $_.ObjectTypeID $BitMask = [convert]::ToString($($ops),2) $BitMaskReverse = ([regex]::Matches($BitMask,'.','RightToLeft') | ForEach {$_.value}) -join '' 0..($BitMaskReverse.Length - 1) | ForEach-Object{ if($BitMaskReverse.Substring($_, 1) -eq 1){ $BitFlag = [math]::Pow(2, $_) $result = Get-CimInstance -Namespace $ns -Query "SELECT * FROM SMS_AvailableOperation WHERE ObjectTypeID=$typeId and BitFlag=$BitFlag" -ComputerName $server $rules.AddRange(@([pscustomobject]@{TypeName = $result.ObjectTypeName; OperationName = $result.OperationName}) -as [psobject[]]) } } } return $rules } $r1 = _getRoles $role1 | Sort-Object -Property TypeName, OperationName $r2 = _getRoles $role2 | Sort-Object -Property TypeName, OperationName function _normalizeList{ Param( [parameter(position=0)] [System.Collections.Generic.List[psobject]] $list ) $tmp = @{} $list.TypeName | Get-Unique | ForEach-Object { $tn = $($_) $val = ($list | Where-Object {$_.TypeName -eq $tn}).OperationName -join ',' $tmp.Add($tn,$val) } return $tmp } $list1 = _normalizeList $r1 $list2 = _normalizeList $r2 $allkeys = $list1.Keys + $list2.Keys | Sort-Object | Get-Unique $final = [System.Collections.Generic.List[psobject]]::new() foreach($key in $allkeys){ if($list1[$key]){ $val1 = $list1[$key] } else{ $val1 = '' } if($list2[$key]){ $val2 = $list2[$key] } else{ $val2 = '' } if($DiffOnly -eq $false -or $val1 -ne $val2){ $final.AddRange(@([pscustomobject]@{TypeName = $key; $($role1) = $val1; $($role2) = $val2}) -as [psobject[]]) } } $final | Out-GridView
  26. hi there worst case scenario while you are troubleshooting the problem you can create bootable media in ConfigMgr, to boot the laptops (usb or cd) and then image them as normal. But as regards your problem, are you sure that the task sequence deployed contains the new boot image ? and it's distributed to all dp's ?
  27. I need some help :) I upgraded to current branch 2006 and now pxe is broken. I updated from 1806 directly to 2006. I upgraded windows ADK and and WinPE and deleted all old boot images, now I have them in SCCM as the only images (both x64 and x86). I've distributed them to my distribution points, it immediately says it's successful to my main sccm server/distribution point but it fails to distribute to my remote DPs. I'll get to that later. I've enabled PXE on the distribution point and I checked the box to "enable pxe support for clients" and everything else on this page is checked including "Enable a PXE responder without windows deployment service". I do NOT have a remoteinstall folder any longer, which i know is correct since i'm not using WDS, and the main DP DOES have the ConfigMgr PXE Responder Service now and is running. I'm getting hella errors on smspxe.log and i don't know what to do going forward. I honestly feel like the new boot image files are not in a place where they can be read and used and I'm stuck. Here's the errors i'm getting in smspxe.log when I try to do a pxe boot: I've uninstalled pxe/reinstalled and deleted the boot images and re-added them / redistributed them and i'm stuck. Anyone have any clues/pointers? This is for k-12 education and we're behind on needing to reimage laptops for some students. Any help is GREATLY appreciated! Packet: Operation: 1 (request), AdrType: 1, AdrLen: 6, HopCount: 0, TransactID: 79570544, BootTime: 4, Addr: 28:d2:44:05:57:79:00:00:00:00:00:00:00:00:00:00, HostName: , BootFile: , ClientIP: 0.0.0.0, HostIP: 0.0.0.0, ServerIP: 0.0.0.0, RelayIP: 0.0.0.0 Options: 53, 1, MsgType: 01, discover 55, 36, ParamRequestList: 01 02 03 04 05 06 0b 0c 0d 0f 10 11 12 16 17 1c 28 29 2a 2b 32 33 36 3a 3b 3c 42 43 80 81 82 83 84 85 86 87 57, 2, MsgMaxSize: 04 ec 97, 17, UUID: 00 81 af 95 4b cf 52 cb 11 ac 21 b0 70 31 06 f9 76 93, 2, Arch: 00 00 94, 3, UNDI: 01 02 01 60, 32, ClassID: PXEClient:Arch:00000:UNDI:002001 SCCMPXE 9/14/2020 12:10:47 PM 9692 (0x25DC) PXE: Packet from 0.0.0.0 (DHCP, 00:15:5D:12:64:02, 10.80.17.27). SCCMPXE 9/14/2020 12:10:47 PM 9692 (0x25DC) Packet: Operation: 1 (request), AdrType: 1, AdrLen: 6, HopCount: 0, TransactID: 79570544, BootTime: 4, Addr: 28:d2:44:05:57:79:00:00:00:00:00:00:00:00:00:00, HostName: , BootFile: , ClientIP: 0.0.0.0, HostIP: 0.0.0.0, ServerIP: 0.0.0.0, RelayIP: 0.0.0.0 Options: 53, 1, MsgType: 01, discover 55, 36, ParamRequestList: 01 02 03 04 05 06 0b 0c 0d 0f 10 11 12 16 17 1c 28 29 2a 2b 32 33 36 3a 3b 3c 42 43 80 81 82 83 84 85 86 87 57, 2, MsgMaxSize: 04 ec 97, 17, UUID: 00 81 af 95 4b cf 52 cb 11 ac 21 b0 70 31 06 f9 76 93, 2, Arch: 00 00 94, 3, UNDI: 01 02 01 60, 32, ClassID: PXEClient:Arch:00000:UNDI:002001 SCCMPXE 9/14/2020 12:10:47 PM 9692 (0x25DC) PXE: 28:D2:44:05:57:79: Operation=1, MessageType=1, Architecture=0, Continuation=0 SCCMPXE 9/14/2020 12:10:47 PM 2748 (0x0ABC) PXE: Packet from 0.0.0.0 (DHCP, 00:15:5D:12:64:02, 10.80.17.27). SCCMPXE 9/14/2020 12:10:47 PM 9692 (0x25DC) PXE: 28:D2:44:05:57:79: Parsed a discover/solicit packet. SCCMPXE 9/14/2020 12:10:47 PM 2748 (0x0ABC) PXE: 28:D2:44:05:57:79: 4B95AF81-52CF-11CB-AC21-B0703106F976: Client is 32-bit, BIOS, Firmware. SCCMPXE 9/14/2020 12:10:47 PM 2748 (0x0ABC) PXE: 28:D2:44:05:57:79: Operation=1, MessageType=1, Architecture=0, Continuation=0 SCCMPXE 9/14/2020 12:10:47 PM 9308 (0x245C) PXE: 28:D2:44:05:57:79: Parsed a discover/solicit packet. SCCMPXE 9/14/2020 12:10:47 PM 9308 (0x245C) PXE: 28:D2:44:05:57:79: 4B95AF81-52CF-11CB-AC21-B0703106F976: Client is 32-bit, BIOS, Firmware. SCCMPXE 9/14/2020 12:10:47 PM 9308 (0x245C) PXE: 28:D2:44:05:57:79: Prioritizing local MP http://MPS-SCCM.magnoliaschools.net. SCCMPXE 9/14/2020 12:10:47 PM 2748 (0x0ABC) PXE: 28:D2:44:05:57:79: Prioritizing local MP http://MPS-SCCM.magnoliaschools.net. SCCMPXE 9/14/2020 12:10:47 PM 9308 (0x245C) Not in SSL. SCCMPXE 9/14/2020 12:10:47 PM 2748 (0x0ABC) RequestMPKeyInformation: Send() failed. SCCMPXE 9/14/2020 12:10:47 PM 2748 (0x0ABC) PXE: 28:D2:44:05:57:79: Unsuccessful in getting MP key information. 0x80004005. SCCMPXE 9/14/2020 12:10:47 PM 2748 (0x0ABC) PXE::MP::InitializeTransport failed; 0x80004005 SCCMPXE 9/14/2020 12:10:47 PM 2748 (0x0ABC) PXE::MP::IsKnownMachine failed; 0x80070490 SCCMPXE 9/14/2020 12:10:47 PM 2748 (0x0ABC) Not in SSL. SCCMPXE 9/14/2020 12:10:47 PM 9308 (0x245C) RequestMPKeyInformation: Send() failed. SCCMPXE 9/14/2020 12:10:47 PM 9308 (0x245C) PXE: 28:D2:44:05:57:79: Unsuccessful in getting MP key information. 0x80004005. SCCMPXE 9/14/2020 12:10:47 PM 9308 (0x245C) PXE::MP::InitializeTransport failed; 0x80004005 SCCMPXE 9/14/2020 12:10:47 PM 9308 (0x245C) PXE::MP::IsKnownMachine failed; 0x80070490 SCCMPXE 9/14/2020 12:10:47 PM 9308 (0x245C) Packet: Operation: 1 (request), AdrType: 1, AdrLen: 6, HopCount: 0, TransactID: 79570544, BootTime: 6, Addr: 28:d2:44:05:57:79:00:00:00:00:00:00:00:00:00:00, HostName: , BootFile: , ClientIP: 0.0.0.0, HostIP: 0.0.0.0, ServerIP: 0.0.0.0, RelayIP: 0.0.0.0 Options: 53, 1, MsgType: 01, discover 55, 36, ParamRequestList: 01 02 03 04 05 06 0b 0c 0d 0f 10 11 12 16 17 1c 28 29 2a 2b 32 33 36 3a 3b 3c 42 43 80 81 82 83 84 85 86 87 57, 2, MsgMaxSize: 04 ec 97, 17, UUID: 00 81 af 95 4b cf 52 cb 11 ac 21 b0 70 31 06 f9 76 93, 2, Arch: 00 00 94, 3, UNDI: 01 02 01 60, 32, ClassID: PXEClient:Arch:00000:UNDI:002001 SCCMPXE 9/14/2020 12:10:49 PM 9692 (0x25DC) PXE: Packet from 0.0.0.0 (DHCP, 00:15:5D:12:64:02, 10.80.17.27). SCCMPXE 9/14/2020 12:10:49 PM 9692 (0x25DC) Packet: Operation: 1 (request), AdrType: 1, AdrLen: 6, HopCount: 0, TransactID: 79570544, BootTime: 6, Addr: 28:d2:44:05:57:79:00:00:00:00:00:00:00:00:00:00, HostName: , BootFile: , ClientIP: 0.0.0.0, HostIP: 0.0.0.0, ServerIP: 0.0.0.0, RelayIP: 0.0.0.0 Options: 53, 1, MsgType: 01, discover 55, 36, ParamRequestList: 01 02 03 04 05 06 0b 0c 0d 0f 10 11 12 16 17 1c 28 29 2a 2b 32 33 36 3a 3b 3c 42 43 80 81 82 83 84 85 86 87 57, 2, MsgMaxSize: 04 ec 97, 17, UUID: 00 81 af 95 4b cf 52 cb 11 ac 21 b0 70 31 06 f9 76 93, 2, Arch: 00 00 94, 3, UNDI: 01 02 01 60, 32, ClassID: PXEClient:Arch:00000:UNDI:002001 SCCMPXE 9/14/2020 12:10:49 PM 9692 (0x25DC) PXE: 28:D2:44:05:57:79: Operation=1, MessageType=1, Architecture=0, Continuation=0 SCCMPXE 9/14/2020 12:10:49 PM 3120 (0x0C30) PXE: Packet from 0.0.0.0 (DHCP, 00:15:5D:12:64:02, 10.80.17.27). SCCMPXE 9/14/2020 12:10:49 PM 9692 (0x25DC) PXE: 28:D2:44:05:57:79: Parsed a discover/solicit packet. SCCMPXE 9/14/2020 12:10:49 PM 3120 (0x0C30) PXE: 28:D2:44:05:57:79: 4B95AF81-52CF-11CB-AC21-B0703106F976: Client is 32-bit, BIOS, Firmware. SCCMPXE 9/14/2020 12:10:49 PM 3120 (0x0C30) PXE: 28:D2:44:05:57:79: Operation=1, MessageType=1, Architecture=0, Continuation=0 SCCMPXE 9/14/2020 12:10:49 PM 8340 (0x2094) PXE: 28:D2:44:05:57:79: Parsed a discover/solicit packet. SCCMPXE 9/14/2020 12:10:49 PM 8340 (0x2094) PXE: 28:D2:44:05:57:79: 4B95AF81-52CF-11CB-AC21-B0703106F976: Client is 32-bit, BIOS, Firmware. SCCMPXE 9/14/2020 12:10:49 PM 8340 (0x2094) PXE: 28:D2:44:05:57:79: Prioritizing local MP http://MPS-SCCM.magnoliaschools.net. SCCMPXE 9/14/2020 12:10:49 PM 3120 (0x0C30) PXE: 28:D2:44:05:57:79: Prioritizing local MP http://MPS-SCCM.magnoliaschools.net. SCCMPXE 9/14/2020 12:10:49 PM 8340 (0x2094) Not in SSL. SCCMPXE 9/14/2020 12:10:49 PM 3120 (0x0C30) RequestMPKeyInformation: Send() failed. SCCMPXE 9/14/2020 12:10:49 PM 3120 (0x0C30) PXE: 28:D2:44:05:57:79: Unsuccessful in getting MP key information. 0x80004005. SCCMPXE 9/14/2020 12:10:49 PM 3120 (0x0C30) PXE::MP::InitializeTransport failed; 0x80004005 SCCMPXE 9/14/2020 12:10:49 PM 3120 (0x0C30) PXE::MP::IsKnownMachine failed; 0x80070490 SCCMPXE 9/14/2020 12:10:49 PM 3120 (0x0C30) Not in SSL. SCCMPXE 9/14/2020 12:10:49 PM 8340 (0x2094) RequestMPKeyInformation: Send() failed. SCCMPXE 9/14/2020 12:10:49 PM 8340 (0x2094) PXE: 28:D2:44:05:57:79: Unsuccessful in getting MP key information. 0x80004005. SCCMPXE 9/14/2020 12:10:49 PM 8340 (0x2094) PXE::MP::InitializeTransport failed; 0x80004005 SCCMPXE 9/14/2020 12:10:49 PM 8340 (0x2094) PXE::MP::IsKnownMachine failed; 0x80070490 SCCMPXE 9/14/2020 12:10:49 PM 8340 (0x2094) Packet: Operation: 1 (request), AdrType: 1, AdrLen: 6, HopCount: 0, TransactID: 79570544, BootTime: 10, Addr: 28:d2:44:05:57:79:00:00:00:00:00:00:00:00:00:00, HostName: , BootFile: , ClientIP: 0.0.0.0, HostIP: 0.0.0.0, ServerIP: 0.0.0.0, RelayIP: 0.0.0.0 Options: 53, 1, MsgType: 01, discover 55, 36, ParamRequestList: 01 02 03 04 05 06 0b 0c 0d 0f 10 11 12 16 17 1c 28 29 2a 2b 32 33 36 3a 3b 3c 42 43 80 81 82 83 84 85 86 87 57, 2, MsgMaxSize: 04 ec 97, 17, UUID: 00 81 af 95 4b cf 52 cb 11 ac 21 b0 70 31 06 f9 76 93, 2, Arch: 00 00 94, 3, UNDI: 01 02 01 60, 32, ClassID: PXEClient:Arch:00000:UNDI:002001 SCCMPXE 9/14/2020 12:10:53 PM 9692 (0x25DC) PXE: Packet from 0.0.0.0 (DHCP, 00:15:5D:12:64:02, 10.80.17.27). SCCMPXE 9/14/2020 12:10:53 PM 9692 (0x25DC) Packet: Operation: 1 (request), AdrType: 1, AdrLen: 6, HopCount: 0, TransactID: 79570544, BootTime: 10, Addr: 28:d2:44:05:57:79:00:00:00:00:00:00:00:00:00:00, HostName: , BootFile: , ClientIP: 0.0.0.0, HostIP: 0.0.0.0, ServerIP: 0.0.0.0, RelayIP: 0.0.0.0 Options: 53, 1, MsgType: 01, discover 55, 36, ParamRequestList: 01 02 03 04 05 06 0b 0c 0d 0f 10 11 12 16 17 1c 28 29 2a 2b 32 33 36 3a 3b 3c 42 43 80 81 82 83 84 85 86 87 57, 2, MsgMaxSize: 04 ec 97, 17, UUID: 00 81 af 95 4b cf 52 cb 11 ac 21 b0 70 31 06 f9 76 93, 2, Arch: 00 00 94, 3, UNDI: 01 02 01 60, 32, ClassID: PXEClient:Arch:00000:UNDI:002001 SCCMPXE 9/14/2020 12:10:53 PM 9692 (0x25DC) PXE: 28:D2:44:05:57:79: Operation=1, MessageType=1, Architecture=0, Continuation=0 SCCMPXE 9/14/2020 12:10:53 PM 9388 (0x24AC) PXE: Packet from 0.0.0.0 (DHCP, 00:15:5D:12:64:02, 10.80.17.27). SCCMPXE 9/14/2020 12:10:53 PM 9692 (0x25DC) PXE: 28:D2:44:05:57:79: Parsed a discover/solicit packet. SCCMPXE 9/14/2020 12:10:53 PM 9388 (0x24AC) PXE: 28:D2:44:05:57:79: 4B95AF81-52CF-11CB-AC21-B0703106F976: Client is 32-bit, BIOS, Firmware. SCCMPXE 9/14/2020 12:10:53 PM 9388 (0x24AC) PXE: 28:D2:44:05:57:79: Operation=1, MessageType=1, Architecture=0, Continuation=0 SCCMPXE 9/14/2020 12:10:53 PM 10212 (0x27E4) PXE: 28:D2:44:05:57:79: Parsed a discover/solicit packet. SCCMPXE 9/14/2020 12:10:53 PM 10212 (0x27E4) PXE: 28:D2:44:05:57:79: 4B95AF81-52CF-11CB-AC21-B0703106F976: Client is 32-bit, BIOS, Firmware. SCCMPXE 9/14/2020 12:10:53 PM 10212 (0x27E4) PXE: 28:D2:44:05:57:79: Prioritizing local MP http://MPS-SCCM.magnoliaschools.net. SCCMPXE 9/14/2020 12:10:53 PM 9388 (0x24AC) PXE: 28:D2:44:05:57:79: Prioritizing local MP http://MPS-SCCM.magnoliaschools.net. SCCMPXE 9/14/2020 12:10:53 PM 10212 (0x27E4) Not in SSL. SCCMPXE 9/14/2020 12:10:53 PM 10212 (0x27E4) RequestMPKeyInformation: Send() failed. SCCMPXE 9/14/2020 12:10:53 PM 10212 (0x27E4) PXE: 28:D2:44:05:57:79: Unsuccessful in getting MP key information. 0x80004005. SCCMPXE 9/14/2020 12:10:53 PM 10212 (0x27E4) PXE::MP::InitializeTransport failed; 0x80004005 SCCMPXE 9/14/2020 12:10:53 PM 10212 (0x27E4) PXE::MP::IsKnownMachine failed; 0x80070490 SCCMPXE 9/14/2020 12:10:53 PM 10212 (0x27E4) Not in SSL. SCCMPXE 9/14/2020 12:10:53 PM 9388 (0x24AC) RequestMPKeyInformation: Send() failed. SCCMPXE 9/14/2020 12:10:53 PM 9388 (0x24AC) PXE: 28:D2:44:05:57:79: Unsuccessful in getting MP key information. 0x80004005. SCCMPXE 9/14/2020 12:10:53 PM 9388 (0x24AC) PXE::MP::InitializeTransport failed; 0x80004005 SCCMPXE 9/14/2020 12:10:53 PM 9388 (0x24AC) PXE::MP::IsKnownMachine failed; 0x80070490 SCCMPXE 9/14/2020 12:10:53 PM 9388 (0x24AC) Packet: Operation: 1 (request), AdrType: 1, AdrLen: 6, HopCount: 0, TransactID: 79570544, BootTime: 18, Addr: 28:d2:44:05:57:79:00:00:00:00:00:00:00:00:00:00, HostName: , BootFile: , ClientIP: 0.0.0.0, HostIP: 0.0.0.0, ServerIP: 0.0.0.0, RelayIP: 0.0.0.0 Options: 53, 1, MsgType: 01, discover 55, 36, ParamRequestList: 01 02 03 04 05 06 0b 0c 0d 0f 10 11 12 16 17 1c 28 29 2a 2b 32 33 36 3a 3b 3c 42 43 80 81 82 83 84 85 86 87 57, 2, MsgMaxSize: 04 ec 97, 17, UUID: 00 81 af 95 4b cf 52 cb 11 ac 21 b0 70 31 06 f9 76 93, 2, Arch: 00 00 94, 3, UNDI: 01 02 01 60, 32, ClassID: PXEClient:Arch:00000:UNDI:002001 SCCMPXE 9/14/2020 12:11:01 PM 9692 (0x25DC) PXE: Packet from 0.0.0.0 (DHCP, 00:15:5D:12:64:02, 10.80.17.27). SCCMPXE 9/14/2020 12:11:01 PM 9692 (0x25DC) Packet: Operation: 1 (request), AdrType: 1, AdrLen: 6, HopCount: 0, TransactID: 79570544, BootTime: 18, Addr: 28:d2:44:05:57:79:00:00:00:00:00:00:00:00:00:00, HostName: , BootFile: , ClientIP: 0.0.0.0, HostIP: 0.0.0.0, ServerIP: 0.0.0.0, RelayIP: 0.0.0.0 Options: 53, 1, MsgType: 01, discover 55, 36, ParamRequestList: 01 02 03 04 05 06 0b 0c 0d 0f 10 11 12 16 17 1c 28 29 2a 2b 32 33 36 3a 3b 3c 42 43 80 81 82 83 84 85 86 87 57, 2, MsgMaxSize: 04 ec 97, 17, UUID: 00 81 af 95 4b cf 52 cb 11 ac 21 b0 70 31 06 f9 76 93, 2, Arch: 00 00 94, 3, UNDI: 01 02 01 60, 32, ClassID: PXEClient:Arch:00000:UNDI:002001 SCCMPXE 9/14/2020 12:11:01 PM 9692 (0x25DC) PXE: 28:D2:44:05:57:79: Operation=1, MessageType=1, Architecture=0, Continuation=0 SCCMPXE 9/14/2020 12:11:01 PM 9524 (0x2534) PXE: 28:D2:44:05:57:79: Parsed a discover/solicit packet. SCCMPXE 9/14/2020 12:11:01 PM 9524 (0x2534) PXE: Packet from 0.0.0.0 (DHCP, 00:15:5D:12:64:02, 10.80.17.27). SCCMPXE 9/14/2020 12:11:01 PM 9692 (0x25DC) PXE: 28:D2:44:05:57:79: 4B95AF81-52CF-11CB-AC21-B0703106F976: Client is 32-bit, BIOS, Firmware. SCCMPXE 9/14/2020 12:11:01 PM 9524 (0x2534) PXE: 28:D2:44:05:57:79: Operation=1, MessageType=1, Architecture=0, Continuation=0 SCCMPXE 9/14/2020 12:11:01 PM 3216 (0x0C90) PXE: 28:D2:44:05:57:79: Parsed a discover/solicit packet. SCCMPXE 9/14/2020 12:11:01 PM 3216 (0x0C90) PXE: 28:D2:44:05:57:79: 4B95AF81-52CF-11CB-AC21-B0703106F976: Client is 32-bit, BIOS, Firmware. SCCMPXE 9/14/2020 12:11:01 PM 3216 (0x0C90) PXE: 28:D2:44:05:57:79: Prioritizing local MP http://MPS-SCCM.magnoliaschools.net. SCCMPXE 9/14/2020 12:11:01 PM 9524 (0x2534) PXE: 28:D2:44:05:57:79: Prioritizing local MP http://MPS-SCCM.magnoliaschools.net. SCCMPXE 9/14/2020 12:11:01 PM 3216 (0x0C90) Not in SSL. SCCMPXE 9/14/2020 12:11:01 PM 9524 (0x2534) Not in SSL. SCCMPXE 9/14/2020 12:11:01 PM 3216 (0x0C90) RequestMPKeyInformation: Send() failed. SCCMPXE 9/14/2020 12:11:01 PM 9524 (0x2534) PXE: 28:D2:44:05:57:79: Unsuccessful in getting MP key information. 0x80004005. SCCMPXE 9/14/2020 12:11:01 PM 9524 (0x2534) RequestMPKeyInformation: Send() failed. SCCMPXE 9/14/2020 12:11:01 PM 3216 (0x0C90) PXE::MP::InitializeTransport failed; 0x80004005 SCCMPXE 9/14/2020 12:11:01 PM 9524 (0x2534) PXE: 28:D2:44:05:57:79: Unsuccessful in getting MP key information. 0x80004005. SCCMPXE 9/14/2020 12:11:01 PM 3216 (0x0C90) PXE::MP::IsKnownMachine failed; 0x80070490 SCCMPXE 9/14/2020 12:11:01 PM 9524 (0x2534) PXE::MP::InitializeTransport failed; 0x80004005 SCCMPXE 9/14/2020 12:11:01 PM 3216 (0x0C90) PXE::MP::IsKnownMachine failed; 0x80070490 SCCMPXE 9/14/2020 12:11:01 PM 3216 (0x0C90)
  1. Load more activity
  • Newsletter

    Want to keep up to date with all our latest news and information?
    Sign Up
×
×
  • Create New...