Comments on: Microsoft UC Client Deployment Script

By: Steve

Steve — Tue, 15 Mar 2011 14:57:25 +0000

I thought I had local copy turned off. It works now. Thanks.

By: Steve

Steve — Tue, 15 Mar 2011 14:19:44 +0000

I tried changing INSTALLATION_ROOT to both of your suggestions and both times I get “could not access source” errors.

By: Curtis Johnstone

Curtis Johnstone — Mon, 14 Mar 2011 20:05:40 +0000

You should be able to do that by just leaving the INSTALLATION_ROOT null (i.e. = “”), or by setting it = “.” (reference the current directory).

I am not sure which one would be best in the SCCM case. I would try setting it = “.”

Hope that helps,
Curtis

By: Steve

Steve — Mon, 14 Mar 2011 19:06:28 +0000

This script is great. I plan on deploying it using SCCM. How can I prevent it from requiring a source path and just run from where the source files are stored? I’d like the files copied from the SCCM DPs and run from the local SCCM cache folder.

By: Curtis Johnstone

Curtis Johnstone — Fri, 19 Nov 2010 16:50:06 +0000

Hi Ryan, glad the script was useful for you – it was a lot of work

My understanding is that the MSI would kick-off, detect Communicator is installed, and do nothing if it was the same or newer version. If that is not the case it is an easy fix.

Starting at line 1070, the script checks to see if Communicator is already installed, and what version. If you want, you can just ‘do nothing’ if a version of Communicator newer than MOC 2005 is installed. You could add this at line 1092:

If (communicatorCurrentVersion >= “2.0″) Then
g_communicatorInstalled = True
WScript.Sleep 1000
WriteToLogFile logFileSection & “Office Communicator Installation Finished”
Exit Sub
End If

Regards,
Curtis

By: Ryan

Ryan — Thu, 18 Nov 2010 22:54:56 +0000

Thank you for the script, works almost perfectly! I have the wsf script set to apply at computer start up and it goes through perfectly. The only issue is that every time a person restarts, the script runs again and the client is installed again. Is there a simple switch I can put it to not run the script if Communicator 2007R2 is already installed?

By: Gordon

Gordon — Wed, 25 Aug 2010 04:28:43 +0000

Thanks for the script. My GPO skills are a bit rusty and I’m having difficulty getting it to apply. I think my issue may be that I can’t do what I want (run as a startup script but limit to specific users on certain machines).

I’d like to have it run on laptops in an OU the GPO is applied to, but only for users in a specific Security Group. We have configured the script as startup script and set the security to allow read/apply for the test security group.

By: Curtis Johnstone

Curtis Johnstone — Wed, 26 May 2010 04:42:32 +0000

Hi,
This problem and the patch for it look really old – it was fixed by the June 2009 update for Communicator 2007 R2. You can use the script today to include a fix for this. Just incorporate the latest Communicator 2007 R2 .msp update file into the .msi file that the script points to – that will install Communicator (i.e. you can apply patches to an install file).

The latest Communicator 2007 R2 release is from April 2010 – this will include a fix for your issue and many more issues. You can download the corresponding .msp file here: http://support.microsoft.com/kb/978564.

By: Steven

Steven — Mon, 24 May 2010 21:33:18 +0000

Link to patch…if anyone needs it.

http://support.microsoft.com/kb/969695/

By: Steven

Steven — Mon, 24 May 2010 21:28:02 +0000

Great script. Works as advertised. Keep up the good work!!

I have an issue with my 64x computers. I keep getting this error as described by Microsoft.

http://support.microsoft.com/kb/972085/

I apply the patch they mention and it fixes the problem. I was wondering if you could incorporate the patch into your script or is there a way to add the patch myself?

Thanks