Jump to content


Jorgen Nilsson

Moderators
  • Posts

    481
  • Joined

  • Last visited

  • Days Won

    30

Everything posted by Jorgen Nilsson

  1. Hi, It sounds like the content is missing on the DP or could be that the bolundaries are wrong and no content can be located. Are there a local DP there? Content avalable? Boundaries and Boundary Groups correct? Regards, Jörgen
  2. Hi, It is described here: http://blogs.technet.com/b/system_center_configuration_manager_operating_system_deployment_support_blog/archive/2011/10/14/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx Option 66 and configuring a boot file is not recommended and you should use IP Helpers instead which should already be inplace as your client will get IP addresses from tjhis computer. What are you trying to configure with option 66 and what error are you seeing? Regards, Jörgen
  3. Hi, With normal autoupdates I assume Windows Update directly in this case? Then create a Collection with all the laptops and create a custom client setting that turns of the SCCM managing the Software Updates and deploy that to the collection with the laptops, then the laptops will start using Windows Update again. Regards, Jörgen
  4. Hi, The Powershell module that is refeered to above can be found here and can of course be used as well. http://www.snowland.se/powershell/sccm-posh/ Regards, Jörgen
  5. Also make sure that Domain Computers have permission to the file share you are using as that is the account that the script will run under which is a different as well from when you run it as a user. Regards, Jörgen
  6. Hi, It is most likely related to the drivers you install, how do you apply the drivers? driver package? apply drivers? What if you try without drivers does it work then? Regards, Jörgen
  7. Hi, That specific update can actually be deployed as an update using SCCM or WSUS http://blogs.technet.com/b/michaelgriswold/archive/2013/03/13/kb2775511-deployment-for-the-sccm-admin.aspx as it is availble in the Microsoft Update Catalog. I normally use a script which can be used as well. http://ccmexec.com/2012/02/installing-multiple-windows-7-hotfixes-msu-with-sccm/ With the runtime execeeded what maximum runtime did you set? it takes a while to install that update as it contains 90+hotfixes. Regards, Jörgen
  8. Hi, Have you followed these instructions and created an .MST file for Itunes? http://msiworld.blogspot.com.au/2012/06/re-packaging-apple-itunes-10617-and.html Regards, Jörgen
  9. Hi, The Configuration Manager Manager Client Upgrade is normally created when you create a MDT Task Sequence, it is the full client as well but as you normally would create a new package for OSD as the builin package/program is read-only. For the updates it the latest one you should deploy, "R2 CU3 - x64 client Updates" and the x86 and deploy them to the clients. Regards, Jörgen
  10. Hi, Did you use a GPO to assign the client installation back in SCCM 2007 ? the GPO is tatooing so it will still point to the old SCCM 2007 environment, could that be the issue? Regards, Jörgen
  11. Looks like a good start, a lot of things to add, as Peter wrote what you can deploy to a collection, etc, Sample queries would hepful as well, Subselect query for quering which computer doesn't have a specific software installed for instance is a must. /Jörgen
  12. Hi, What options did yoyu set? the error translates to: The operation timed out Source: Winhttp Sounds like a firewallm/communication/proxy issue.. Regards, Jörgen
  13. What if you remove the credentials from the batch filke and use Run this tstep as the following account instead.. Regards, Jörgen
  14. Hi, I would assume it could be the path, the task sequence enginge runs in 32 bit on the client so the path C:\Program Files (x86)\ will not exist or be just C:\Program Files instead. Try check the option " Disable 64-bit file system redirection" and try again, then it will be executed in 64 bit environment or change the path. Regards, Jörgen
  15. Hi, Yes it works just fine to move a DP like that,done it many times. Make sure to remove it from all the boundaries / boundary groups when it is not used so that clients don't try to contact it when you have it in your office and update it. So when it is not used have it attached in the office so that it can be updated, then when you move it you assign it to a Boundary Group. Regards, Jörgen
  16. Hi, As you ar uninstalling three different softwares with a script you detection method should identify all three as detection methods and the command you want to run as uninstall, under the uninstall command, then you deploy it as intent: Uninstall and the detection method will detect that all three where removed. Regards, Jörgen
  17. Hi, As answered above,ccmsetup.exe is smart enough to choose the correct plattform for the client. Replicing your GPO is a good idea, Jason Sandys have written a great Startup Script that can be used instead, which is much miuch better. http://blog.configmgrftw.com/configmgr-client-startup-script/ It is also smart enough to install the correct CU update for the client and much more. I use it basically for all implementations. Regards, Jörgen
  18. Hi, I always create a "Vanilla" package with all the updates available for each OS at the time of installation of ConfigMgr 2012 to catch all computers that perhaps needs an old update, troubleshooting where an update is uninstalled and so on. Then I create the ADR's so that all future updates are deployed using them. Automate everything! /Jörgen
  19. Hi, You should be able to copy all the WMI queries from your models to the Apply Drivers step and then use the IF NONE option.. From Technet: None Select this option if none of the conditions contained in the If Statement can evaluate to True for the If Statement to evaluate to true. This option is equivalent to a Boolean NOT AND.
  20. Hi, If you uinstall Configuation manager 2007 ikt sholuld remove the entries automatically, if you just turn of the server, delete them, they are not needed anymore and can always cause issues in the future. Regards, Jörgen
  21. Hi, That is correct, you cannot push out WI-fi profiles that uses a pre-shared key/password... :-( Regards, Jörgen
  22. Hi, No you must run that step as it does much more than just install the client, it sets it to provisoning mode as well.. The best solution I can come up with is to build the image in MDT = no SCCM client and as you say to speed up things add Office in the image it takes a long time to install and even longer to upfate. You don't have any issues with updates that requires multiple reboots either, there are many benefits of using MDT to build the master image. Regards, Jörgen
  23. Hi, To uninstall the clients you need to execute C:\Windows\CCMSEtup\ccmsetup.exe /uninstall you can put it as a GPO Startup script or run it as a schedule task via a GPO and set it to run once.. Or use SCCM 2012 and deploy the command as a package/program Regards, Jörgen
  24. Hi, It is just the way SCCM 2012 works ;-) All content will be placed on the Primary site server and then sent from there to the DP's, So yes you will see all the content there, You could add a "cheaper" disk to your primary site server and move the SCCMContentLib to that disk using the tool: http://blogs.technet.com/b/neilp/archive/2013/01/08/configuration-manager-2012-sp1-content-library-transfer.aspx Regards, Jörgen
  25. Hi, Install the MDT Toolkit and enable the MDT integration, after that you can create an MDT User-Driven OS Deployment Task Sequence and then you can in the MDT UDI Editor create your own page and then set a TS variable based on that choice. Then you should be able to retire the .HTA Regards, Jörgen
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.