Standalone primary. No lag. Weeks go by since a TS change like a core app, 1 out of 50 device experiences the issue. U can pxe boot 5-10 device at the same time one can experience this behavior all others are fine, pxe boot that same device and it completes like the rest of the Devices. I collected the logs and what I stated before its like a phantom TS for the one device. It's not often but one out fifty will exhibit this. Never experienced this in any other environment. And it is not a complex one at that.
Sent from my iPhone On Apr 4, 2014, at 6:10 PM, "Niall Brady" <[email protected]<mailto:[email protected]>> wrote: well what type of environment do you have ? a standalone primary or more than one (with CAS), when lag occurs I test it by changing the name of a task sequence by adding or removing a fullstop (for example) so Windows 7 x64 Ent becomes Windows 7 x64 Ent. when you PXE boot, if you see the wrong one then you know it's lagging. And that problem requires troubleshooting of the primary server itself to see why policy is slow to update, quite likely that some other activity like collection updates (queries) is driving it crazy On Fri, Apr 4, 2014 at 11:22 PM, Max Erenburg <[email protected]<mailto:[email protected]>> wrote: I started an engagement where I believe I am experiencing the same behavior. Client is running CM12 SP1 RTM (which I though maybe the issue as SP1 can be patched up to CU4). 1 out of 50 roughly) PXE booted devices fail to build successfully because TS is targeting an old package which no longer exists in CM. E.g. Client packaged a new Adobe Reader version and retired prior package (removed from CM). TS is referencing that nonexistent package ID and name (was correct when the package did exist), clearly failing to install. I started collecting the logs, it happens when connecting with any DP and communicating with any MP, so its not isolated to a particular server. Reboot the same device and PXE boot once again and it will build successfully. Its the first time I have run into this myself with CM. Being that we will be upgrading them to 2012 R2, I figured not to waste time troubleshoot further and would resolve with upgrade. Until you posted you are on R2... now I have to wonder. ________________________________ From: [email protected]<mailto:[email protected]> [[email protected]<mailto:[email protected]>] On Behalf Of Michael Timm [[email protected]<mailto:[email protected]>] Sent: Friday, April 04, 2014 4:00 PM To: <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Cached OSD gah sorry should've added that in. Sccm 2012 R2 no cu's. Sent from my iPhone On Apr 4, 2014, at 1:48 PM, "Max Erenburg" <[email protected]<mailto:[email protected]>> wrote: What version of CM (and if any CU version applied) are you running? ________________________________ From: [email protected]<mailto:[email protected]> [[email protected]<mailto:[email protected]>] On Behalf Of Michael Timm [[email protected]<mailto:[email protected]>] Sent: Friday, April 04, 2014 3:41 PM To: <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Cached OSD No, pxe. Sent from my iPhone On Apr 4, 2014, at 1:37 PM, "Niall Brady" <[email protected]<mailto:[email protected]>> wrote: are you starting the task sequence from within Windows ? On Fri, Apr 4, 2014 at 9:24 PM, Michael Timm <[email protected]<mailto:[email protected]>> wrote: Curious if anyone has run into this before. When we re-image a machine, it seems to pull down a cached version of my Task Sequence. I run a light image, all third party applications are installed after the OS is installed. When we re-image a machine it installs everything in the TS, but they are old versions that aren't advertised. If we run it through OSD again, it lays down the correct TS with the updated applications. All new machines are getting the correct OS and applications. Am I nuts? Or is there some setting I'm missing? Thanks, Mike T. Sent from my iPhone ________________________________ CONFIDENTIALITY NOTICE: This message is intended only for the use and review of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message solely to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify sender immediately by telephone or return email. Thank you. ________________________________ CONFIDENTIALITY NOTICE: This message is intended only for the use and review of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message solely to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify sender immediately by telephone or return email. Thank you. ________________________________ CONFIDENTIALITY NOTICE: This message is intended only for the use and review of the individual or entity to which it is addressed and may contain information that is privileged and confidential. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message solely to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify sender immediately by telephone or return email. Thank you.
