Jump to content


dooty22

Established Members
  • Posts

    16
  • Joined

  • Last visited

dooty22's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. wouldnt you normally just do the updates/software etc during the task sequence ?? Otherwise id need to re-capure the image every time something changed. or am I misunderstanding.
  2. ok thanks. So if I want to deploy the base vanilla OS source as is, then there is no requirement for the build and capture process.
  3. and probably a dumb question, but Im confused what this process does. It seems to deploy a WIM from Installation source, then copy up that WIM and push a copy back to a share again, which you use within a task sequence. Why dont you just directly use the WIM from the installation source ?
  4. Im interested in using one in an upcoming deployment to monitor client installation issues but finding it difficult get information. The following seems to only apply to sccm 2007. https://technet.microsoft.com/en-au/library/bb680830.aspx Im interested in a few things namely: - Is there an issue installing the role on an existing DP or does it need its own server ? - Any pre-req's ? - How is the information displayed or what information I do get from setting one up ? Is it in status messages or do I run reports or ? - Does it generate much traffic (ie Will reporting to the FSP from clients at remote locations be an issue or do I need an FSP at each remote site? any advice appreciated.
  5. Strange issue where site wide client push is enabled, but only for Servers and ConfigMgr site Systems. Workstations is unchecked. However, if I check my ccm.log, I can see it attempting to connect to Workstation OS's to install the client. Could anyone explain this behaviour ? Does it use the AD object properties to decide whether its a workstation OS ? What is even stranger is that some of the workstations in the ccm.log which its attemping to push the client to, already have the client installed !?!
  6. Is this even possible ?? I think you either use PXE or you boot from an exported ISO (ie USB or DVD) to get WinPE loaded and connect to your WDS/DP server and start the Task sequence. Otherwise you're using offline task sequence media.
  7. Just wondering, will enabling this in a 2012 environment, upgrade existing 2007 clients ? (assuming the 2007 clients have been discovered and are appearing in 2012)
  8. so i found the issue on other clients pointing to a server problem. I couldnt find any issues in any of the logs or eventvwr. I ended up removing all the adr's and packages, removing the sup role, removing the wsus server role, deleting the wsus database, then re-adding everything again from scratch, configuring it exactly the same, and now I have updates coming down again. Seems like a sledgehammer fix but there we go.
  9. im also seeing this in the updatesdeployment.log No current service window available to run updates assignment with time required = 1 Im getting a suspicion that because so many updates are needed, some calculation on the time required to run them all is exceeding some limit...somewhere...but I dont know how to verify that. as i said earlier im 100% certain that no maintenance windows are configured.
  10. well windowsupdate.log shows it detecting the correct wsus server, and has detected over 100 required updates. Schedules them for 19.00 local time, then nothing happens daily at that time. No errors in the log at all. im stumped !
  11. Yes enabled Software Updates in the client. As i mentioned, other clients are getting updates ok, its this one client. Anything specifically Peter ? I have an ADR, which runs monthly, it creates a new update group and automatically creates and enables the deployment. The schedule on the ADR is set to be available "as soon as possible", so is the deadline. It is set to allow installation outside of maintenance windows, all updates go into the same single package every month (and I see this is pushed successfully to the DP after the last run of the ADR) I have a single standalone site server (svr-3.core.net) which is the SUP, and a single DP (svr-2.core.net). The client is definitely in the targetted collection, the cm client is active healthy etc.
  12. I have an interesting case and Im stuck with this. I have everything set with auto-deploy rules etc, and updates seem to be deploying ok to other clients. I have one windows 7 vm, fresh vanilla install and updates refuse to deploy to it. A test software deployment of adobe reader deployed fine. The updatesdeployment.log shows it scanning and adding alot of updates to a deployment schedule. Alot of entries like this (hundreds) Update (Site_46872716-190B-45ED-B651-80F57364D553/SUM_3ae68db3-72a1-4f93-8e68-75bb8e07823e) added to the targeted list of deployment ({e547f70c-419f-41d9-89e1-5c507200e82f}) Then I have this A user-defined service window(non-business hours) is available. We will attempt to install any scheduled updates. Attempting to install 0 updates No actionable updates for install task. No attempt required. and this repeats over and over and has been for maybe a week now. The wuahandler log suggests it has correctly registered the sup Existing WUA Managed server was already set (http://SVR-3.CORE.NET:8530), skipping Group Policy registration . Some other searching suggested a maintenance window issue. Since this is a lab environment I have only 4 collections and its easy to confrirm i have no maintenance windows, and the srs report confirms this. I also went and removed all the user "work hours' from software center. The deployment is scheduled as available and then a deadline which has passed over a couple of months ago. I also have no group policies for auto-updates set in the domain. I notice if I look at windows update control panel on the client itself that auto-update is not enabled, and its asking me to enable it. I havent done this yet because i figure i shouldnt have to, it might ruin the test case, and the cm client should be taking care of it id have thought. if anyone has any hints on where i go next with this or logs to check, wld be much appreciated cheers
  13. what extra functionality does integrating mdt actually give you ?
  14. along with the other suggestions cant you also just allow updates to install silently in the background and suppress the reboot to prevent disruption to users.
  15. thats probably all the convincing I need. Its always much easier applying these sort of updates when the installation is fresh and before it goes into production. Considering also at this stage I have not pushed out the cm2012 client to anything. Once a site has been upgraded to whatever CU, will the default client that it deploys match that CU version ?? or do you need to push out the base client, then subsequently update it ??
×
×
  • Create New...