OS Deployment Thread, WDS vs WAIK vs MDT vs SCCM in Technical Quick Intro I see a lot of talk with all these different deployment tools but Im finding it tricky. SCCM 1706 is now available to install and this step by step SCCM 1706 Upgrade Guide will help you to install the upgrade based on best practices. SCCM SCUP Enterprise Administration Guide. SCCM deployments and SCUP. System Center Updates Publisher SCUP is a stand alone tool that is used in conjunction with Microsofts System Center Configuration Manager CM hereafter to allow administrators to more accurately and efficiently install and update software. Together, CM and SCUP are Microsofts latest change and configuration management solution that replaces older methodologies such as SMS and GPO. Unlike those technologies, CM provides features such as metering, asset intelligence, and improved remote client administration. For example, CM users can easily determine what products versions are installed including all dot and double dot patches without having to write a complicated query. SCUP is a catalog system and is very convenient for those who use it, but doing so is not required. As the successor to SMS, SCCM can deploy without SCUP. Other supported deployment methods include bootstrapper and AIP. Patch Servers With Sccm 2012 Metering DeviceNote. This documentation is for administrators familiar with managing networked environments via CM. CM documentation. For details about using CM and SCUP, refer to Microsofts documentation. Available catalogsSCUP files are hosted on a public server for manual or scripted download as needed. There are two types of files cab cab files are the actual catalog. Learn the basics of using Microsoft System Center Configuration Manager to manage client operating systems, distribute software, track inventory, and more. System Center Configuration Manager sccm 2012, sccm 2007, ConfigMGR 2012, ConfigMGR 2007, System Center Configuration Manager. The following SCUP catalogs are available Update ready for distribution. System requirements1. The SCUP catalogs for 1. DC products require the items documented at http www. In particular, SCUP 5. The use of 4. 5 throws the error The update failed Software. Update. Rules validation. Note that 1. 1. x SCUP catalogs used to push updates from Win 8 Windows Server 2. WSUS v. 3. 0 SP2 3. The SCUP catalogs for 1. SCUP 4. 5. All other requirements are defined by the Microsoft System Center Configuration Manager 2. Note. The following table lists the base software used in Adobes lab environment. Administrators should refer to Microsofts documentation for information on installing and configuring the requisite components. Every enterprise environment will be unique, and many configurations are possible. Tested softwareSoftware. Notes. Operating System. Windows Server 2. Admins should follow the Microsoft documentation and use whatever is appropriate for their environment. Internet Information Services IIS7. NET Framework 3. 5. Web. DAV 7. 5. The Background Intelligent Transfer Service BITS enabled distribution point role requires BITS server extensions and Web. DAV extensions. Database. Microsoft SQL Server 2. Microsoft Management Console 3. MMCFramework that unifies and simplifies day to day system management tasks. Microsoft Report Viewer Redistributable 2. Windows Server 2. CM R2 requires WSUS 3. SP2. Do not install WSUS 3. SP1 on Windows Server 2. R2. Active Directory 2. Defines computers the CM controls. Site servers may need to be a member of an Active Directory domain depending on the network architecture. Windows Server Update Services 3. WSUSDistributes the updates. Only the administrator console component is required, and it must be installed prior to SCUP,SCUP 4. System Center Updates PublisherPublishes updates to WSUS. The Acrobat catalog requires version 4. System Center Configuration Manager 2. SP2 CMConfiguration Manager 2. R2 is not a full product version and requires that SP1 or SP2 already be installed before running Configuration Manager 2. R2 Setup. SCCM SCUP basicsNote. SCCM users should note that SCUP catalogs cant deliver anything but a generic installer. Because enterprises use different configurations, there is no way for Adobe to provide installers tailored to individual organizations. However, MSPs do not change existing settings, and MSI deployments always involve using an MST to migrate settings. Best practicesUpdate validation before deployment. Verify patch installation on the intended target for a manual install first outside SCCM context. Dont test deployments during SCCM server changes. Be patient While operations appear to return UI control back to the user immediately i. Run Synchronization, some operations are batch processes that run in the background and take some time to complete. Always Run Synchronization after integrating a SCUP catalog. Doing so ensures the WSUS and Configuration Manager Console gets synchronized. Refresh often Often once a task completes, updates may not appear in the various UI components and you may not see changes take affect. Always refresh using the Refresh link or context sensitive menu item. Consider whether or not you should mark an expiration time deadline for publication. Once an update has expired, it will no longer be offered by the SCCM client. If you accidentally choose the wrong date or use the wrong UTC date setting, updates wont be issued in the managed client. Define boundaries for the managed environment. Ensure all your managed clients are hosted within the desired domain, and that clients that should not be managed similarly are outside of that domain. For example, you could have an Active Directory Server define the managed domain anything outside that domain will not be managed by my SCCM server. Do not delete SCUP catalog components. Deleting the catalog component in SCUP simply deletes the SCUP reference to the package component i. Reader English 9. Always expire a no longer used component to ensure its synchronized with the WSUS server and Configuration Manager Console before deletion. Otherwise, dangling pointers will prevent you from expiring the actual WSUS package component without some serious hacks. Do not use prerequisite rules in the catalog. For 1. 0. x deployments, consider not using Supersedence as SCUP 4. Supersedence properly. Catalog importThis section provides a short example using SCUP 4. There is one catalog for Reader and one for Acrobat. The file names are static, so scripted downloads should be relatively straightforward. Note. It may also be useful to understand the differences between quarterly updates, out of cycle patches, and the possible file types. While SCUP catalogs provide a way to automate installs, you should understand what gets installed and why. For example, Acrobat updating always involves installing every MSP update in order. Reader updates may involve quarterly MSI files that dont require installing previous updates. To import the SCUP catalog Download the catalog for your product. In the SCUP Console, choose Actions Import Updates. Choose Single Catalog Import. Choose Next. Browse to the downloaded catalog. Click Accept Adobe as a Trusted Publisher and then click OK. After import, the a summary screen displays information about the current updates. You are now ready to deploy updates using the CM defined workflow. SCUP Imported update catalog. Troubleshooting FAQsWhy does my install fail with a dependency does not exist errorWhen the WSUS database is not properly synced, you may see the following error Publish. Item UpdateReader XI English Upgrade Update. Id c. 44. 8bd. 67 9e. Vendor Adobe. Systems,Inc. Product Adobe Reader cannot be published as its dependency5. WSUS. Updates. Publisher. To fix this issue, resync the WSUS database to get the requisite public detectoids. There is no way to push these through SCUP as it is used for only third party updates. The dependencies listed in your log are the detectoids for X8. Microsoft x. 86 based systems 3. E0. AFB1. 0 A9. FB 4c. A6. 0E 5. 79. 0C3. E2. E9 4f. 71 8. FF5. 88. 52. 79. 78. These are not authored by Adobe and as per the message in the log must be present in the WSUS database. Why dont I see the 1. MUI installer in the 1. SCUP catalog The current SCUP catalog does not list the 1. MUI Reader. While most updates and out of cycle security patches are language agnostic, MUI installs require using a MUI update if there is one. Because the 1. 1. MUI specific update does not appear in the catalog, this update must be applied outside of the SCCM SCUP update process. Note. This bug will be fixed in future catalog versions, and the issue only exists in the 1. To fix the problem, do one of the following Why dont I see all the updates after importing the SCUP catalog Sometimes there are refresh issues on the backend and the latest update might not appear immediately after a release. If this happens, verify the update appears in Microsofts list of partner catalogs. You an also import the update manually or post on the Adobe forum. WDS vs WAIK vs MDT vs SCCM Quick Intro. I see a lot of talk with all these different deployment tools but Im finding it tricky to figure out how they relate to one another, which ones supercede others and just in general how they work and what they do. Now Ive been in IT for about 1. I feel Ive picked up a hell of a lot in that time Im still relatively green so forgive me for any inaccuracies I make in this and subsequent posts. Also the more info you guys can give the better for me WDS, WAIK, MDT and SCCMCould someone give me a brief run down on each of these and how they work together. What each one does and whether any of them supercede the others For example do you still need WDS if you have SCCM set up SPECIFICS I WANT TO DO Anyway Ill tell you where we were and where we are now and perhaps you guys could give me an idea on where to move to next. GHOST So in ye olden days we had an old ghost cast server. Youd F1. 2 and PXE boot into RIS on the same server, select the relevant GHOST boot image with the correct DOS Drivers for the network card then the reset was just the standard connecting to the Ghost Cast Server and capturing deploying an image. This worked ok for a while but I decided we should move away from GHOST because it was getting harder to find DOS drivers that worked for newer machines and this led to alot of issues with clients dropping out mid imaging not being able to connect in the first place. WDSSo I spend a week or so reading up on WDS. Installed it on a blank 2. K8. R2 server and configured it. All in all it was pretty easy and took about two hours to get it up and running and capturing images. It seems to me that WDS is pretty much the same as GHOST. Create a base image. PXE boot to the network and then capture it so you can deploy it later on. Immediately though I found it loads better than the previous GHOST server because we had no issues connecting to the WDS server well apart from one set of laptops but injecting the drivers into the boot image was easy to fix. It was also a lot quicker to capture and deploy and we had no issues with clients dropping out half way through. Also learning to use Sysprep has enabled me to learn about automating certain things with the newly imaged machines such as auto joining the domain we still put the computer name in manually using minisetup. Can you believe in the olden days we didnt use Sysprep and instead manually connected all imaged computers to the domain and run NEWSID Madness I still have nightmares from last summer when I had to image 6. NEWSID Joining The Domain Manually. WHERE DO I WANT TO GO NEXT So this is all working out pretty awesome. A lot better than the old Ghost way we did things however its become obvious that we now have about 8 or 9 different models of PC and Laptops with pretty much exactly the same image and the only difference being they have different hardware and therefore need differing drivers. But it seems stupid having so many images for such a minor change. Ive heard about the ability to create hardware independent images. I was wondering how do I go about doing this and what tools do I need Also something minor but was wondering how to configure naming the computers once theyve been imaged. So far the only real intervention we have from starting to image a machine to it being ready is to put in the machine name. What are the best ways to automate naming the computers so the correct computer gets the correct name when its imaged AND WHERE I WANT TO BE AFTER THIS The next big issue we have is regarding things like Flash and Patches for programs like Seriff and whatnot. At the moment end users have to bring there laptops to us and we log them off, log on as admin and update it for them. This is a pain in the arse. Believe there is a way to use some of the deployment tools to push out updates to client computers but I have no idea how to do it and again what technologies I need to use. Can anyone help Also Im interested in making things a bit more Zero Touch. Possibly pushing out deployments from the server instead of going round the rooms. FINWhoa. that is one hell of TL DR right there. Hope some of you guys will be kind enough to give me some help with this I know I can probably find all this on my own however I really think asking on here is going to give me the direct answers to the questions I have and hopefully some of the more experienced on here can give me some pointers and examples of how they set things up. I find it easier to see how other people have done things and working out how that works opposed to reading through a 4.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |