jvargas

Hi everyone I currently noticed that strange data transmissions are being carried out when staging workstations. Defining stragne: When staging a client, between 200MB and 480MB of data is being transmitted from the MP to the workstation. After some digging, I determined that this is being sent over port 8530, which of course is from the SUP of this primary site. In the task sequences we always install the software updates. On the MP, there is also the SUP role active for this primary site. I know, the workstations are receiving the metadata and catalogue info from the SUP of their primary site. But 200-480MB?! Especially as the binaries reside on the workstation's local DP. I am left alone on this one and it is puzzling me quite a bit. Any ideas? All input welcome

Same "issue" here There are no errors and problems with the USMT-process, but the "Migration Status" never changes after a successful migration from "In progress" to anything else. What I also am quite confused of is the fact that the linked data on the State migration point is still in place after deleting items via SCCM console in "User State Migration".

How can I finid out the encryption-key in a SCCM2012 environment? edit: Okay, okay ... Found it ... At least I guess so. Assets and Compliance\User State Migration Right Click on a Client View Recovery Information

Well well ... Solved this. I had to install WSUS on the Primary Site as well. Although the options were set already, it looks like the binaries of the WSUS simply were missing to ensure connectivity with the clients. Thanks for the help!

Alright - Sorry for not responding. Been quite busy. So, since I didn't set up the environment by myself I cannot really tell you how it has been set up. But I can tell that all the other features and roles seem to work absolutely proper. After going through the Post here on the page http://www.windows-noob.com/forums/index.php?/topic/5683-using-system-center-2012-configuration-manager-part-5-adding-wsus-adding-the-sup-role-deploying-the-configuration-manager-client-agent/]CLICK[/url]. The "Central Access SIte" (CAS) and "Primary Site" (PRI) are consisting of the following systems: CAS - SRV1 + SRV4 ... PRI - SRV2 + SRV3 Role-Definitions can be found in my initial post. I found out some differences: There is no Software Update Point installed on the Primary Site. Only on SRV4 of the Central Access Site. I am not sure about the GPO. Did not have time to check this today. Although looking at this point as is: We do not deploy the CM-Client via GPO. Subsequently to the point above (GPO), the Option "Software-Update Based Client Installation" is not activated. Cool, kinda happy about that. Already had horror visions about that. To be honest, to me this is a terrible tool to troubleshoot. Even Tomcat is a charm compared to SCCM. Not at all, softwares can be deployed easily and without any interruptions. Don't know about endpoint, we don't use this feature.

It does not say anything about the source when I open Windows Updates via Control Panel. Although it displays me "94 important updates available". Seems like it checks on the WWW for updates, since I only added 24 updates to the Software Update Group on SCCM. I honestly doubt that this is the case at the moment. Why ever that is, it makes not much sense to me. Good question - In which of the 2 billion logfiles would this be logged?

Yeah, I tried both with "As soon as possible" and also with a defined date. Edit: Does this affect the status of the Software Updates? I mean the deadline should not matter if an Update is "Required" or not.

Hi everybody After I have downloaded the first set of updates, subsequently set up the first Software Update Group and assigned it to a Device Collection I defined beforehand, I am currently struggling with the following issue: Not even one single Software Update in the Software Update Group is shown as "Required" in the Console. The clients in the Device Collection are definitely not having these updates installed already. Which should put the status of all the Updates to "Required". To me, this makes absolutely no sense since applications can be deployed without any problems. So it's not basically a communication issue between the client(s) and the backend. The architecture here consists of 4 servers and is set up as the following (NAME - ROLES): SRV1 - Component, Site Server, Site System, Reporting, DB SRV2 - Component, Site Server, Site System, App Catalog, DB, Management Point SRV3 - Component, Site Server, Site System, Distribution Point SRV4 - Component, Site Site System, Software Update Point Some logfile-entries from the client: UpdatesDeployment.log <![LOG[Evaluation initiated for (0) assignments.]LOG]!><time="09:50:44.931-120" date="08-31-2012" component="UpdatesDeploymentAgent" context="" type="1" thread="5272" file="assignmentsmanager.cpp:1108"> <![LOG[Message received: '<?xml version='1.0' ?><SoftwareUpdatesMessage MessageType='EvaluateAssignments'><UseCachedResults>False</UseCachedResults></SoftwareUpdatesMessage>']LOG]!><time="10:06:15.033-120" date="08-31-2012" component="UpdatesDeploymentAgent" context="" type="1" thread="5996" file="cdeploymentagent.cpp:189"> <![LOG[Removing scan history to force non cached results]LOG]!><time="10:06:15.033-120" date="08-31-2012" component="UpdatesDeploymentAgent" context="" type="1" thread="5996" file="assignmentsmanager.cpp:1217"> <![LOG[Assignment({8E213C0E-2B01-46C8-9293-8F9DA552C464}) already in progress state (AssignmentStateDetecting). No need to evaluate]LOG]!><time="10:06:15.065-120" date="08-31-2012" component="UpdatesDeploymentAgent" context="" type="1" thread="5996" file="updatesassignment.cpp:819"> ScanAgent.log <![LOG[- -Processing Scan Job TTL invalidity request]LOG]!><time="09:50:44.915-120" date="08-31-2012" component="ScanAgent" context="" type="1" thread="5272" file="scanjobmgr.cpp:600"> <![LOG[Message received: '<?xml version='1.0' ?> <UpdateSourceMessage MessageType='ScanByUpdateSource'> <ForceScan>TRUE</ForceScan> <UpdateSourceIDs> <ID>{0483E1D4-E0E8-4AE5-8319-7918DF5942BB} </ID> </UpdateSourceIDs> </UpdateSourceMessage>' ]LOG]!><time="10:06:12.707-120" date="08-31-2012" component="ScanAgent" context="" type="1" thread="920" file="cscanagent.cpp:956"> <![LOG[*****ScanByUpdateSource request received with ForceReScan=2, ScanOptions=0x0000000a, WSUSLocationTimeout = 604800]LOG]!><time="10:06:12.707-120" date="08-31-2012" component="ScanAgent" context="" type="1" thread="920" file="cscanagent.cpp:181"> <![LOG[sources are not current]LOG]!><time="10:06:12.723-120" date="08-31-2012" component="ScanAgent" context="" type="1" thread="920" file="utils.cpp:109"> UpdatesHandler.log <![LOG[initiating updates scan for checking applicability.]LOG]!><time="09:39:35.118-120" date="08-31-2012" component="UpdatesHandler" context="" type="1" thread="3552" file="capplicabilityhandler.cpp:434"> <![LOG[successfully initiated scan.]LOG]!><time="09:39:35.290-120" date="08-31-2012" component="UpdatesHandler" context="" type="1" thread="3552" file="capplicabilityhandler.cpp:490"> <![LOG[CUpdatesAgent::FinalConstruct entered]LOG]!><time="09:43:52.719-120" date="08-31-2012" component="UpdatesHandler" context="" type="1" thread="5204" file="cupdatesagent.cpp:48"> <![LOG[initiating updates scan for checking applicability.]LOG]!><time="09:43:52.751-120" date="08-31-2012" component="UpdatesHandler" context="" type="1" thread="5200" file="capplicabilityhandler.cpp:434"> <![LOG[successfully initiated scan.]LOG]!><time="09:43:52.829-120" date="08-31-2012" component="UpdatesHandler" context="" type="1" thread="5200" file="capplicabilityhandler.cpp:490"> I don't have a PatchDownloader.log on any client. So ... Any input would be greatly appreciated, since this stuff is driving me nuts :angry:

As far as I understand your question: You define the download location by defining a Deployment Package. When creating an ADR you can choose a certain Deployment Package, so the Updates get downloaded to this location. Yes, there is. For example, you can set the generated Deployments to not "enable the deployment after this rule is run".

Hi everybody I am also currently working on a future implementation of SCCM2012 Software Updates in our environment. Currently we do not have SCCM in place, so this gives me the advantage of starting from scratch. We will not patch any non-MS products with SCCM, so this narrows it a bit down. The focus is clearly set on Windows 7 and Office 2010. Anyway, to me it seems like the implementation of Software Updates in SCCM2012 is terrible. This conclusion comes from the basic fact that it is simply a mess to work with efficiently. Since we are migrating our whole environment from WXP to W7, we use a base image that includes all the needed software updates to the current date. This gives at least the advantage that all the OS-patches are installed at deployment time. Building up on this fact, we simply will patch the clients on a bi-monthly base. We will not use ADR, since I want to be in charge 100% of what, when, why, where and how. Initially I have thought of the process as follows (Device Collections already created): Evaluate the needed software updates Create the corresponding Software Update Group(s) (eg. W7 Updates 2012-09 / O2012 Updates 2012-09) Download the software updates with the corresponding Deployment Package(s) Assign the software update groups to the Device Collection "Testing" (Phase0) Await feedback of test users Assign the software update groups to the Device Collection "Pilot" (Phase1) Await feedback of pilot users Assign the software update groups to the Device Collection "Production" (Phase2) This is the basic software update cycle. Now, because i do NOT want to have 12 Software Update Groups after one year, the idea is it to create a Software Update Group as a "Software update archive" (one for W7 and one for O2010). These "Software update archives" will be constantly on deployment to ensure compliance throughout the environment. So to make the "Software update archive" effective, the used updates (eg. from W7 Updates 2012-09) get moved to the archive as a new rollout (eg. W7 Updates 2012-10) will be set into production (Phase3). It is surely not an optimal process, but IMHO there is not an optimal process when using SCCM2012 Software Updates. If anybody has some thoughts about this, please feel free to share.

Yes, sure I just posted the changed part, the include part is still as posted above in the first post. Would there be any reason the captured files get skipped when the destination folder does not exist? Because the path "%CSIDL_PROFILE%\AppData\Local\Microsoft\Outlook" does not exist just after setting up Win7.

Well well ... The script also does not seem to work with the modified <locationModify> part. Capturing works according to the scanstate.log, although the restoring still is not taking place somehow.

Hi Peter Thank you very much for your answer. I was throwing an eye on the RelativeMove also, but initially ignored it since I wasn't sure if I could use variables in this combination. So just out of the blue and interpreted in context of my basic idea, this would look like this: <locationModify script="MigXmlHelper.RelativeMove('%USERPROFILE%\Application Data\Microsoft\Outlook\’, '%CSIDL_PROFILE%\AppData\Local\Microsoft\Outlook’)"> <objectSet> <pattern type="File”>%USERPROFILE%\Application Data\Microsoft\Outlook\* [*]</pattern> </objectSet> </locationModify> I surely will give it a try! And I surely will keep you posted on this!

Hi everybody I just encountered an issue while trying to capture and restore custom folders / data with USMT 4.0 in combination of a SCCM2012 state migration point. The capturing task works quite well, I suppose. At least all the settings I did and wanted to capture got captured and restored again from WinXP into Win7. Well, so far the success story ... Since I need to capture more data (Outlook signatures in this first case), I read the documentation on how to do this and created a custom XML-File: <migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/testmigration"> <component type="Documents" context="UserAndSystem"> <displayName>Copy Files from XP Folder A to Win7 Folder B</displayName> <role role="Data"> <rules> <include> <objectSet> <script>MigXmlHelper.GenerateUserPatterns ("File","%USERPROFILE%\Application Data\Microsoft\Outlook\* [*]","TRUE")</script> </objectSet> </include> <locationModify script="MigXmlHelper.Move ('%CSIDL_PPROFILE%\AppData\Local\Microsoft\')"> <objectSet> <script>MigXmlHelper.GenerateDrivePatterns ("* [*]","Fixed")</script> </objectSet> </locationModify> </rules> </role> </component> </migration> Quite simple job, basically. Get the files of the WinXP-Client and restore them back to the Win7-Client to a different location. To my understanding, this should work. But actually, it doesn't Consulting the loadstate-logfile, I unfortunately did not see any errors correlating with the "Copy Files from XP Folder A to Win7 Folder B"-Section. Any help is appreciated Cheers and thanks in advance JV