Windows XP Windows Update Fix

If you are trying to run Windows Update on a Windows XP machine, you may find that you are getting errors or that it gets stuck in a “Searching for updates” process.

This may be that your Windows XP machine has not fully updated its own Windows Update Agent.

To fix this, you should first ensure that you are running on Windows XP Service Pack 3. Once you are, you should then download the Windows Update Agent 3.0 which you can get from the link below.

DOWNLOAD

Windows Update Agent v3.0

INSTRUCTIONS

When you have downloaded the correct version for your machine, you should start a command prompt in admin mode and run the following command:

 C:WindowsUpdateAgent30-x86.exe /wuforce  

Windows XP Windows Update Fix 1

Once this has completed, restart your machine and try to run the Windows Updates again, you should now find that they run without issue.

Windows Updates during SCCM OSD from Replica WSUS Servers

sccm logo

I have been asked to provide a solution to a situation where during SCCM OSD, they want to run Windows Updates across multiple sites worldwide using the local WSUS replica servers.

So as an example, the main Headquarters office is in New York with the main WSUS server and then in Rome there is another site with a replica WSUS server syncronising from the New York server. A new PC is shipped to Rome and takes the SCCM OSD deployment and they want Windows Updates to run from the Rome WSUS server to fully patch the machine to corporate WSUS standards.

Note that SCCM SUP is not used in this environment.

PREREQUISITES

Please note that this guide assumes that you have an advanced knowledge of SCCM, WSUS and MDT.

You must also have MDT integrated in your environment for this to work.

INSTRUCTIONS

So, where do we start? Firstly, you need to identify all the WSUS servers available for each site. For demo purposes, we are going to be using the following sites and WSUS server URL’s:

  • New York City – https://nyc.techygeekshome.info – this will be our main HQ WSUS server
  • Rome – https://rome.techygeekshome.info – local replica server
  • Tokyo – https://tokyo.techygeekshome.info – local replica server

Once you have all the information you require you then need to export the certificate for WSUS from the primary HQ server and put it into a source share as we will be creating a package using this later. Lets create a share called:

\\nyc-cmsource-1\OSD\WSUS

Once you have your WSUS certificate in this share, you also need to add a registry file, this will be used to allow local updates to be published to the client machine. I have already prepared this registry file for you and this can be downloaded from the link below:

Download WSUS Registry Edit

So you should now have a registry file and a WSUS certificate in your source share. You now need to create a package within SCCM using this source share as your source location for the package. We’ll call the package WSUS Certificate Import:

Windows Updates during SCCM OSD from Replica WSUS Servers 2

You then need to create three different programs using this package. One to import the certificate into the Trusted Publisher, one to import the certificate intot he Trusted Root and one to run the registry edit file to enable local updates to run.

You should use the following commands for each program:

  • Import AcceptTrustedPublishedCerts – Regedit.exe -s wsuspolicy.reg
  • Install Trusted Publisher – certutil.exe -addstore -f TrustedPublisher WSUS.cer
  • Install Trusted Root – certutil.exe -addstore Root WSUS.cer

So you should end up with a package with these three programs available from it:

Windows Updates during SCCM OSD from Replica WSUS Servers 3

Please note that you must ensure that you have selected “Allow this program to be installed from the Install Package task sequence without being deployed” on the Advanced tab of the program for this to work:

Windows Updates during SCCM OSD from Replica WSUS Servers 4

You should then distribute this package to your required distribution points so it is ready to use.

When you have completed the package and programs part, you can then move onto the task sequence steps. In this demo I’ll just be showing you the steps for the updating part, however, in a live environment, I strongly suggest that you make these steps the very last part of your task sequence.

TASK SEQUENCE STEPS

In your task sequence there are five stages to getting the updates to install from the local WSUS:

  • MDT Toolkit Package
  • Import of certificates
  • Registry edit to enable local updates
  • Pointing to correct local WSUS server
  • Running of updates

So, the first part of your task sequence steps needs to be to load the MDT Toolkit:

Windows Updates during SCCM OSD from Replica WSUS Servers 5

You should then add the Trusted Root Certificate from the package and program we created earlier:

Windows Updates during SCCM OSD from Replica WSUS Servers 6

Then add the Trusted Publisher Certificate:

Windows Updates during SCCM OSD from Replica WSUS Servers 7

Then add the registry edit file:

Windows Updates during SCCM OSD from Replica WSUS Servers 8

The next set of steps are to add the variables for which local WSUS server to use. So, add a Set Task Sequence Variable step, give it a name for your local WSUS server (in our case it’ll be NYC, Rome & Tokyo), then for each step the Task Sequence Variable should be:

WSUSServer

Then each steps value should be the local WSUS servers URL (as stated at the beginning of this guide):

Windows Updates during SCCM OSD from Replica WSUS Servers 9

Windows Updates during SCCM OSD from Replica WSUS Servers 10

Windows Updates during SCCM OSD from Replica WSUS Servers 11

Now, this is the critical part, before we move away from these steps, you need to add an option condition to each of the Task Sequence Variable steps to identify when the variable is to be used. Although there are other ways, I am going to use the AD Site Name to identify where the client machine is at. So, click on the step for Rome, then click Options:

Windows Updates during SCCM OSD from Replica WSUS Servers 12

Click the Add Condition button and select query WMI. You should then type in the following query to identify that if the client machine matches this query, this step will be activated:

SELECT ClientSiteName FROM Win32_NTDomain WHERE ClientSiteName = “Rome”

Windows Updates during SCCM OSD from Replica WSUS Servers 13
You should do this for each Task Sequence Variable step.

Then, the final part is to actually run the Windows Updates, this is the final step that should be run as a command line.

The command line that should be run is the following:

cscript.exe “%SCRIPTROOT%\ZTIWindowsUpdate.wsf”

Windows Updates during SCCM OSD from Replica WSUS Servers 14

Now when you run these steps in your OSD task sequence, the client machine will identify which site it is on and then install any required updates from the local WSUS server.

CCMClean – Uninstalling Configuration Manager Clients

CCMClean-Featured-Image

You may sometimes come across Configuration Manager clients that are not working correctly. The tell-tale signs for this on a client machine are missing tabs, missing selections under the Actions tab and incorrect or missing information on the General tab. In short, your Configuration Manager Control Panel applet may look like below:

CCMClean - Uninstalling Configuration Manager Clients 15

I have had techs in the past try to fix this using a huge range of ideas including trying to re-install the client back out to the client machine from the server to even manually editing the registry and WMI. Also, the favourite method that I have seen (also on many blog posts and forums) is using:

ccmsetup.exe /uninstall

but in my experience using this method does not fully work and doesn’t clear out the (possible) WMI corruptions, so the only clean way I have found of fixing this is to use a trusted old tool called CCMClean.

To use CCMClean all you have to do is run the single execute file as a local administrator and it will completely remove the Configuration Manager client from the machine. Once it has completed, you should then reboot the machine to ensure a nice clean OS and then you can re-deploy the client as a push from the CM server or as a manual install. You should then notice once the new installation has completed that the machine has a fully working Configuration Manager client installed.

The CCMClean.exe is an older tool and can be a bit tricky to find so you can download this from our downloads microsite:

Download

Download CCMClean

Items to note:

  • CCMClean.exe is not supported by Microsoft so you do use this at your own risk
  • Running the CCMClean.exe straight from the file as I’ve stated above is usually fine on a normal client machine, but be very careful on servers or distribution points as it can remove SCCM roles too
  • To be sure you remote the client only, you should use the /client switch

Screenshots

CCMClean - Uninstalling Configuration Manager Clients 16

If you have any questions about this or require any assistance then please leave a comment at the bottom of this post.

Conclusion

You can go ahead and try the supported way of uninstalling the SCCM client using ccmsetup.exe /uninstall and if it doesn’t work, download CCMClean and give it a go. It won’t cause any harm to your end user maachine.

Once the client is removed, you can then just push the client install back out to the target machine.

Autodesk Products Serial Number Reporting Script Update Version 4.1 – Major Release

Autodesk AutoCAD Logo

We have made some major updates to our Autodesk products serial number reporting script which should fix all of the reporting issues that some people have seen. It also includes a large amount of additional languages and products.

WHAT PRODUCTS ARE INCLUDED?

The list of Autodesk products that this Configuration Item script will now report back to your SCCM database are the following:

  • AutoCAD 2000 – 2014
  • AutoCAD LT 2000 – 2014
  • Autodesk P&ID – 2012 – 2014
  • Autodesk Architecture – 2012 – 2014
  • Autodesk Mechanical – 2012 – 2014
  • Autodesk Building Systems – 2012 – 2014
  • Autodesk Inventor – 2012 – 2014
  • Autodesk Plant 3D – 2012 – 2014
  • Autodesk Civil 3D – 2012 – 2014
  • Autodesk AutoCAD OEM – 2012 – 2014

WHAT LANGUAGES ARE INCLUDED?

  • AutoCAD – English / German / French / Italian / Spanish / Polish / Hungarian / Czech / Russian / Brazilian Portuguese / Simplified Chinese / Traditional Chinese / Korean / Japanese
  • AutoCAD LT – English / German / French / Italian / Spanish / Polish / Hungarian / Czech / Russian / Brazilian Portuguese / Simplified Chinese / Traditional Chinese / Korean / Japanese
  • Autodesk P&ID – English
  • Autodesk Architecture – English
  • Autodesk Mechanical – English
  • Autodesk Building Systems – English
  • Autodesk Inventor – English
  • Autodesk Plant 3D – English
  • Autodesk Civil 3D – English
  • Autodesk AutoCAD OEM – English

HOW DOES IT WORK?

This script runs on your users machines using the Configuration Item process of SCCM 2012. The script is a VBScript so can also be run using .vbs files (using login scripts or Group Policy). This then creates a new WMI class called cm_AutoDesk and will inject the following information into this WMI class:

  • Key Name (registry location of serial)
  • Product Name
  • Release Version
  • Serial Number
  • Standalone Network Type

Once this information is in the users machines WMI, SCCM 2012 can then be configured to collect this information using the Hardware Inventory function.

Full instructions on how to set this up in full can be found below using our step by step guide.

DOWNLOAD

The updated script can be downloaded from the link below:

Download Autodesk Serial Collector Script

INSTRUCTIONS

Full our full step by step guide on setting this up using SCCM 2012, please click the link below:

Step by Step Guide to Report AutoCAD Serial Numbers

The file that you will download on this page is just the script that is used for the Configuration Item and this can be used to replace your current (or you can add as a new) CI in SCCM.

If you have any problems with this, please feel free to leave a comment.

Shoretel Contacts Importer v2.0 Released

Shoretel Orange and Black Logo

UPDATE: Shoretel Contacts Importer v3.0 is now available – click the Downloads button above to obtain

================================================================

We are pleased to announce the release of Shoretel Contacts Importer version 2.0.

This is an update to our previous version which can be found below with full instructions and details on what functions this program carries out.

DOWNLOADS

Get it from CNET Download.com!

INSTRUCTIONS

Full instructions and explanations as to what this program does can be found by clicking here

SCREENSHOTS

Shoretel Contacts Importer v2.0 Released 18

 

Shoretel Contacts Importer v2.0 Released 19

Google Blogger Sitemap Generator Utility Released

google

UPDATE: Google Blogger Sitemap Generator v1.3 is now available – click the Downloads button above to obtain

================================================================

We are pleased to announce the release of Blogger SiteMap Generator v1.0.

This is a small standalone utility that will allow you to enter your Google Blogger URL, select the number of entries that you want adding to your Sitemap and then generate the URL required for your Sitemap.

DOWNLOADS

Google Blogger Sitemap Generator Utility Released 20

INSTRUCTIONS

Once you have downloaded the utility, you should enter your own Google Blogger URL here:

Google Blogger Sitemap Generator Utility Released 21

Please note that you should leave in the https:// part and do not end the URL with a forward slash “/”.

You should then select the approximate amount of post entries that you have on your Blog from the drop down list as this will be the maximum amount that will be added to your sitemap:

Google Blogger Sitemap Generator Utility Released 22

You should then press the Generate button:

Google Blogger Sitemap Generator Utility Released 23

This will then generate your sitemap URL and will be presented to you in the Generated Sitemap URL box:

Google Blogger Sitemap Generator Utility Released 24

You can then copy this generated code to use as your Google Blogger Sitemap. This can then be submitted to sites like Google, Bing and Yahoo!

If you have any questions about this utility then please add your comments below.

Shoretel Communicator Contacts Enabler Install & MSI File Now Released

Shoretel Orange and Black Logo

We are pleased to announce the release of the installer and MSI files for our Shoretel Communicator Contacts Enabler program.

The program was originally released as a standalone utility and that program can be downloaded for free here:

Shoretel Contacts Importer v1.1

The latest version is version 3.0 which can be downloaded for free below:

Shoretel Contacts Enabler v3.0

After a number of requests for the MSI file installer, we have now compiled this release, however, due to ever increasing hosting costs, we must charge a small fee for this installer program. This is not for us to make money, it is simply to be able to provide us with the funds to keep enhancing this website.

Once you have made your payment, you will be provided with a download link for an executable installer and an MSI installer which you can use to mass distribute this fix to your user machines using SCCM, WDS, Group Policy or any other deployment system you may use.

WHAT IS INCLUDED?

Included in the package that you will receive are two MSI files – one for x86 machines and one for x64 machines. We have also included the EXE files for each architecture should you wish to use these as well.

WHAT DOES IT DO?

This installer fixes the issue of Shoretel Communicator version 13 and above not importing your personal contacts from Outlook into your Shoretel Communicator Directory.

By default, the Outlook Import options will look like this:

Shoretel Communicator Contacts Enabler Install & MSI File Now Released 25
If you run this installer program, when you go back into your Shoretel Communicator Outlook Import options, you will find that you can now import all contacts including from Sharepoint lists and Shared Mailboxes.

 

Shoretel Communicator Contacts Enabler Install & MSI File Now Released 26

With us providing the MSI file, you can also mass distribute this fix to your users using programs like SCCM, Group Policy or even from a file share using login scripts.

INSTRUCTIONS

There are a few ways that you can use this installer package, you can either run the setup.exe or setup.msi file and go through the installer wizard, or if you wish to mass distribute using the MSI file, the installer code that you should use is:
 msiexec.exe /i "SCEx64.msi" /q /norestart  

Note that the above is for the x64 installer, obviously change this to SCEx86.msi for the x86 installer.

If you have any questions about this release, please leave your comments below.

SCCM clients stuck on 0% downloading applications

microsoft black logo

If you have a client that is not downloading its required files in the Software Center (having requested from the software catalog and is seemingly stuck on 0%) then it could be an issue with the local DP server.

To fix this, login to the local server and go into IIS Manager. You should then browse to the Application Pools and find the “SMS Distribution Points Pool”, if it is stopped, right click on the pool and click Start.

SCCM clients stuck on 0% downloading applications 27

After doing this, you should find that the clients on the local site will now be able to download from the point distribution server.

Feedback

If you have any feedback or questions on this guide, please feel free to leave us a message in the comments section below.

Installing WSUS Console from the Software Center in SCCM [2019 Updated]

System Center Configuration Manager SCCM

You may wish to add the WSUS console to the Software Center in SCCM. This stops people logging onto WSUS servers and also provides quick and easy access to multiple WSUS servers. However, the installer requires a few setup parameters to make it work correctly. Download WSUS Console Windows Server Update Services Console 3.0 SP2 … Read more

Remove Internet Explorer 10 using SCCM & Software Catalog

I manage a SCCM environment where it was required to have the option to remove Internet Explorer 10 using the Software Catalog. This was due to a number of legacy web based systems not working with IE10 and was to get the end user the ability to remove it if required without the assistance of the busy IT team.

I started to look into this and the solution is very simple. All that is required is to create a custom application in SCCM and instead of giving it an installation source, it just requires the installation program and it is this installation program that carries out the uninstall.

INSTRUCTIONS

You should create a custom application in SCCM but do not add a content source as you will not be requiring any media files to carry out this uninstall.

You should then just input an installation program that will carry out the uninstall. The command for this uninstall is:

 wusa.exe /uninstall /quiet /norestart /KB:2718695  

Note that this should be inserted in the Installation program section, not the uninstall program section. You should then have a Programs tab that looks like this:

Remove Internet Explorer 10 using SCCM & Software Catalog 28

You then need to add a detection method to check that the machine requesting the uninstall has IE9 available for it.

To do this, you should point the detection method at the IE9 executable file and base the setting on the file version. If you point the detection method at IE10 executable, then this application will not run as it will state that you already have it “installed!.

Your detection method should then look like this:

Remove Internet Explorer 10 using SCCM & Software Catalog 29

There is no need to distribute this application as there is nothing to distribute but you should then deploy to where it is required. Test first before pushing out publicly and also not that a reboot must be carried out to complete the uninstall.

If you have any questions about this guide, please post them below in the comments section.