If you are using standard machines as distribution points in your remote offices, the naming might be an issue for you, as it was for us. There was nothing in the naming that distinguished them to allow us to know their location. The only option we had was to keep a spreadsheet list of the machines with the associated location. The easy way around this is to create a distribution point group that allows you to custom name the group. You only associate the one distribution point to that group, which then gives you the custom naming schema you were looking for. When you distribute and deploy software, you select from the distribution point group instead of from the distribution points, thereby allowing for easy dissemination.
26 April 2013
Custom Naming Distribution Points
Related Posts:
Adjust Screen Resolution during Build Sometimes the screen resolution in a build does not set to the maximum. Resolution can be set with PowerShell, but the scripting requirements and complexity is too much, IMO. AutoIT offers an easy way to automate this proce… Read More
Verify applications were installed during build process As many of you have probably experienced, SCCM and MDT do not always install all of the applications that are in the task sequence list, even if it returned an error code 0. This can be rather annoying, especially when it h… Read More
SCCM PowerShell SCUP Alternative I have wanted to be able to update an application on the fly without having to create new application packages in SCCM. This is especially useful for applications that are updated quite frequently, such as Java Runtime Env… Read More
Deploying Autodesk Revit Packages Autodesk makes it very easy to create installation packages for deploying Revit software. The problem is that when executing these deployment packages through SMS/SCCM or integrating them into a build process, the package re… Read More
SCCM Client Installer This PowerShell script will uninstall previous versions of SCCM client, run the CCMClean to make sure all instances of the client are gone off of the machine, and finally install the SCCM client. The script will not complet… Read More
0 comments:
Post a Comment