66945

I think I found the issue - timezones. My Primary server (which I connect to, and create deployments) is located in GMT+3 timezone. The 'affected' office is in GMT-7 timezone; difference of 10 hours. Offices that are not affected are in GMT+8 timezone (i.e. ahead of Primary server) When I create a deployment and select 'required + 'ASAP' (without selecting UTC checkbox) - the deployment is made available at at the current time of the primary server. However, since UTC option is not selected, if deployment was made available at 9am on the Primary server, clients will wait till 9am local time before treating deployment as available. Since the affected office is 10 hours behind the primary server, I had to wait 10 hours before the 'ASAP' deployment will begin on those clients. PEBKAC!

'Downloal content from DP and run locally' for both cases, and clients are allowed to pull from default site boundary group.

Some clients are able to suddenly download and install packages, with this lines appearing in the logs: Program Install Service change to state STATE_ADVANCED_DOWNLOAD content in progress Execution Request for advert PRI2009E package PRI000F8 program Install Service state change from NotExist to AdvancedDownload Somehow clients thought that the content 'did not exist' - any suggestions on how/where to troubleshoot this?

Any tips for that? Content download and installation is working for Applications and Software Updates. The fact that it doesn't work for packages only baffles me and I'm not even sure if the issue is 'content download' related.

Content does not get downloaded as the advertisement does not even appear in Software Center. Basically the client sees the advertisement and does nothing - i.e. it doesn't execute this step: Mandatory execution requested for program System Log and advertisement XXXXXXXX

On clients which are not installing packages, this line is missing in execmgr log: Mandatory execution requested for program System Log and advertisement XXXXXXXX

I tried reinstalling the secondary site that services this problematic office - doesn't help. Changing to IP range boundary groups didn't help too. I just realised - this particular secondary site is the problem; whether it is the office where the site server is, or the remote office - clients are not installing packages at all. Applications/Updates work however. All other secondary sites work fine too.

Before today (problem has been here for weeks) i was using IP address range and AD Site boundaries - for all offices - including those affected and non-affected ones. As part of troubleshooting this issue, I decided to remove IP address range from all boundary groups and use only AD site boundaries. My structure is something like this - Office A + Primary Site (1) + Boundary Group (Site is on same subnet as boundary group) 10.1.0.0/16 Office B + Secondary Site (2) + Boundary Group (Site is on same subnet as boundary group) 10.10.0.0/16 Problem Office C + Secondary Site (2) + Boundary Group (Office is of different subnet than the Secondary Site servicing this office) 10.20.0.0/16

I would like to assume my boundaries are correct - Applications and Windows Updates are deploying (and downloading) correctly. Only packages do the deployment get stuck and content does not get downloaded. That said, it is occasionally possible to make a package download and install - i think it was by reinstalling client, but it doesn't work 100% of the time. Which drives me bald.

Policy arrived for child program Install WinPcap execmgr 3/26/2018 8:57:06 PM 4076 (0x0FEC) Policy arrived for child program Install Wireshark execmgr 3/26/2018 8:57:06 PM 4076 (0x0FEC) Policy arrived for child program NI Count execmgr 3/26/2018 8:57:06 PM 4076 (0x0FEC) Policy arrived for child program Settings execmgr 3/26/2018 8:57:06 PM 4076 (0x0FEC) Policy arrived for child program Install Service execmgr 3/26/2018 8:57:06 PM 4076 (0x0FEC) Policy arrived for parent package PRI000F9 program * execmgr 3/26/2018 8:57:06 PM 4076 (0x0FEC) Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="PRI000F9",ProgramID="*", actionType 6l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l execmgr 3/26/2018 8:57:06 PM 4076 (0x0FEC) Raising event: [SMS_CodePage(437), SMS_LocaleID(1033)] instance of SoftDistProgramOfferReceivedEvent { AdvertisementId = "PRI20095"; ClientID = "GUID:61A17DFE-EB8E-40C8-8C62-D7F5756AC1C1"; DateTime = "20180327025706.984000+000"; MachineName = "AZ-FS"; ProcessID = 6076; SiteCode = "PRI"; ThreadID = 4076; }; execmgr 3/26/2018 8:57:06 PM 4076 (0x0FEC) As above, the policy arrive, and then nothing - client doesn't proceed any further, no errors whatsoever.

for example, with a 'required' package deployment execmgr shows that agent received the 'advertisement' in the correct flow of events, one would expect the advertisement to then kick off the installation/execution - but that doesn't happen content is not downloaded the deployment doesn't appear in software center either reinstalling client seems to help - but only once; subsequently deployments require a re-installation each time the agent definitely is talking to the MP and knows about the deployment; but it merely receives the deployment and doesn't proceed to do anything. there are no errors in execmgr. for a 'working pc', you might expect 10 lines of logs (for a successful and complete deployment) but for agents in this remote office of mine, there are only 4 lines of logs (just an example) - and the remaining lines (steps) are missing with no errors at all (and the 4 lines of logs are 'correct' - i.e. they are what's supposed to appear for working deployments)

anyone able to help save whatever hair i have left?

This is one of my worst experiences with SCCM. I have a secondary site located in office X. Then, I have a small remote office Y without any local site servers (DP, MP, etc) so all PCs there will pull from the secondary site server in office X. Application & Software Update deployment and CPI works fine over S2S VPN from office X > Y. However, package deployments just don't work. I create various package deployments (some with, some without content) - they are all stuck at 'In Progress - Program Received'. I see no errors in the logs at all - at best, the logs show me that 'nothing' is happening, i.e. the PC/agent sees the advertisement, and then does nothing (the next logical step is proceed to execute the package commands, which it doesn't) My boundary groups are set up correctly. The very same packages, if I deploy to a different office (A with local site server on the same LAN), works flawlessly. Can anyone help me before I lose all my hair...

I am trying to upgrade Windows 10 instances that were installed using en-US media and have language packs applied to them. As you may know, this will fail if the upgrade media is en-US (i.e. does not correspond to the language pack that has been applied to the OS). I am trying to workaround this issue by rebooting into WinPE before starting the Upgrade step. In WinPE I will use DISM to change the system UI language to en-US which should allow the upgrade to proceed (I will apply necessary language packs and UI settings in a later step). The step works fine and I am able to change the system UI language successfully in WinPE. The next step reboots the system into the OS, with the following step the 'actual' upgrade step. However, after the system reboots from WinPE into the OS, the 'upgrade' step does not run - there is no progress UI or anything (although I can see TSManager.exe and OSDUpgradeWindows.exe running in the background. Looking at the SMSTS.log, OSDUpgradeWindows.exe is constantly trying to validate certificate (effectively a loop) - is that why the task sequence never continues?

Hi! I have an OS Deployment task sequence that basically formats the HDD and installs fresh copy of Windows 10 (it is not in-place upgrade per se since it actually formats the PC entirely). This task sequence works perfectly fine when deployed via PXE boot. However, I tried to deploy it to 'ConfigMgr Clients only' and that's when I had an issue. The task sequence is suppose to appear in Software Center; but of the 3 clients I tested it with, it only appears in the Software Center for a Windows 8.1 PC (and is able to install just fine). For the other 2 Windows 10 (1607) PCs, the task sequence doesn't appear in Software Center at all, no matter how I get it to sync the policies. Anyone knows what am I missing? Thanks!

Hi, My console crashed and I'm trying to unlock the locked object (a task sequence). I tried using the Unlock-Object cmdlet in PowerShell but it fails with this error: Unlock-CMObject -InputObject $(Get-CMTaskSequence -Name Test) Unlock-CMObject : Cannot unlock object. Object context '874f0b81-e922-4ebe-94a5-3c3bfaeba50d' is different than the current session context '7eead30c-5325-4087-9c20-8f0396c0c3ec'. At line:1 char:1 + Unlock-CMObject -InputObject $(Get-CMTaskSequence -Name Test) + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (Microsoft.Confi...ckObjectCommand:UnlockObjectCommand) [Unlock-CMObject], SmsException + FullyQualifiedErrorId : ObjectLocked,Microsoft.ConfigurationManagement.Cmdlets.Common.Utility.UnlockObjectCommand How can I target the 'correct session context'? I only have 1 Primary Site and the PowerShell session is connected to that Primary Site.

Hi! Has anyone managed to get it working? I know it was broken in MDT2013 U1. I have since updated MDT from 2013 U1 to 2013 U2. I created a new task sequence (and also new boot image, new toolkit package, new settings package) after the update - I assume these steps are needed for 'U2' to kick in / take effect. However, I copied the tasks from a previous task sequence into this new task sequence (since it already had all the tasks I needed) - I believe it should be ok to re-use the 'tasks'. The task sequence takes an install.wim and installs Windows to a new VM - along with other configuration such as joining domain, etc. However, when Windows installation is complete, there is no language pack installed. But there are not errors in the task sequence log either. Is it still broken or am I missing something? Thank you.

Hi, Using SCCM OSD to deploy Windows 10 - I created a 'dynamic' unattend.xml file to be used during the 'Apply Operating System' task sequence. But somehow the system locale and home location (GEOID) settings are not applied successfully. I had used the same unattend file for W8.1 deployments and it worked fine. Am I supposed to do it differently for Windows 10? Below is the answer file (the %OSD******% variables are declared/set using 'Set Task Sequence Variable' task sequence executed just before the 'Apply Operating System' task sequence. Thank you.

Any has any ideas? It is irreversibly eating up disk space on my distribution point. Whenever I remove any package from a DP via the CM12 console - it doesn't get removed from the folder on the DP server itself.

I deleted them from the CM12 console - but I only removed them from the DP (not the entire hierarchy). (the packages still exist on other DPs)

Hi, I removed some packages from a distribution point (but I didn't remove the package from SCCM) but the used disk space on the distribution point didn't decrease at all - 10's of GB were removed. How can I clean up the undeleted files? Is there a way to force the distribution point to compare against what SCCM says it has VS what remains on the share/folders? Everything in \SCCMContentLib\FileLib is obscurely named so I couldn't do it manually even if I wanted to.

Hi Niall, Is the above scenario still valid if I combine offline servicing (for the WIM) and online windows updates (during TS)? I always assumed this will mean the OS will be fully patched / most up to date once the TS completes. Generally I configure ADR to remove superseded updates. I will agree though that the purely task sequence method of deployment takes much longer (from deployment start till end) - however zero/lite-touch it may be.

Hi, Almost all of the guides I've read online regarding OS deployment involves building and capturing a 'baseline' OS image and then using task sequences to deploy the captured/baseline image. It is almost like installing OS manually, configuring it - then backing it up and restoring to a new machine (just without the customization ability via task sequences). I took a different approach and simply deploy the standard (unmodified) Windows image and use only task sequences to modify the resulting installation into a final, user-ready state. This achieves 99% of what I need. I don't 'build and capture' anything at all. It also gives me great flexibility/agility since I do not have to re-build and re-capture and re-distribute the 'baseline' image should there be any changes required - I just make changes to the task sequences, click Apply, wait a minute or two for the change to replicate across the organization and Done! I am ready to deploy the updated task sequence in just minutes. Am I missing something? What are the benefits/use cases for 'building and capturing'?

Hmm I don't quite understand "should never use the Auto APply functionaly". It seems like a perfectly fine function other than the 'bug/issue' with W10 + E7XX0. One drawback of 'Install Driver Package' is it becomes a requirement for the package to be available on the distribution point during deployment - even if you do not intend to deploy that driver package to the laptop (i.e. it's for a different laptop model) (do correct me if I am wrong) I use one master task sequence to deploy OS to all laptops across the organization - different offices have different laptops. The master task sequence contains driver installation for over 10 different laptops (each it's own separate step). With 'Auto Apply Drivers', I group drivers for each laptop into their own respective categories. Using task sequence conditions, I configure the task sequence to 'auto apply' only ABC drivers if it is a ABC laptop, etc. When the task sequence runs, it doesn't try to validate if the driver package exists on the distribution point. (because 'auto apply' doesn't have such requirement) With 'Install Driver Package', I need to deploy all the driver packages listed/referenced in this master task sequence to all the distribution points. If I know that XYZ office only has ABC laptops, then I only need/want to distribute the driver package for ABC laptops to this office. This way, I can use one master task sequence for the different offices without having to distribute all the possible/referenced driver packages to all the distribution points. (i.e. 1 master task sequence for 10 different laptops - but each office's distribution point only needs to store driver packages of laptops in that office)

Hi Geopar, I have encountered the same issue. Referring to http://blogs.technet.com/b/msdeployment/archive/2015/09/15/mdt-2013-update-1-re-released-build-8298.aspx, it's a known issue: