SCCM 2007 - Uninstall user rights installed program

We are facing some issue when we want to uninstall Programs in Windows 7 which have been installed with the logged on user’s rights.
We are using SCCM 2007 and have packages installing “Only when a user is logged on” and “Run with user rights”. We did this way package to run with user rights due to the application functionality.
But the problem comes when we try to Uninstall the current package, we run a vbs script with admin rights to uninstall the current version before the install of the upgraded version, the VBS scripts runs with admin rights and a result the can’t the application
under programs and features on the system.
When we run the .vbs script with user right it work for the only that user who had previously logged on to that pc, so if the second user logs on get error when uninstalling the pervious application as it was installed under his user rights.
I know this is a very tricky situation but can please help.
Regards,
Sabi

execute the un-install from SCCM by means of a package and run it under the system account
https://technet.microsoft.com/en-sg/library/gg682013.aspx?f=255&MSPPError=-2147217396
Blog: http://theinfraguys.com
Follow me at Facebook
The Infra Guys Facebook Page
Please remember to click Mark as Answer on the answer if it helps you in anyway

Similar Messages

SCCM 2007 agent fails top install...

Hello,
The installation on two clients from 3 are failing with the following:
No client is currently installed. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
Installing version 4.00.6487.2000 of the client with product code {2609EDF1-34C4-4B03-B634-55F3B3BC4931} ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
MSI PROPERTIES are CCMHTTPPORT="80" CCMHTTPSPORT="443" INSTALL=ALL ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
There are no certificate(s) that meet the criteria. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
Failed in GetCertificate(...): 0x80040281
ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
File 'C:\Windows\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi' doesn't have a valid digital signature. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
A Fallback Status Point has not been specified. Message with STATEID='316' will not be sent. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
Why these agents are suddenly failing to install as more than 1,000 succeeded..
Same OU as others
Same Subnet as others
Thanks,
Dom
System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

The top listed error message are meaningless and not fatal.
Note that posting a couple of out of context messages is completely meaningless though. Please post the entire relevant, unedited snippets of the ccmsetup.log file.
Jason | http://blog.configmgrftw.com | @jasonsandys
Hello,
Here the complete ccmsetup.log
==========[ ccmsetup started in process 6456 ]========== ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
Version: 4.0.6221.1000 ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /mp:configmgrsrv.ad ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
CCMHTTPPORT: 80 ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
CCMHTTPSPORT: 443 ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
CCMHTTPSSTATE: 2147483648 ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
CCMHTTPSCERTNAME: ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
FSP: ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
Config file: ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
Retry time: 10 minute(s) ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
MSI log file: ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
MSI properties: CCMHTTPPORT="80" CCMHTTPSPORT="443" ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
Source List: ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
MPs: ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
configmgrsrv.ad ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
Updated security on object C:\Windows\ccmsetup\. ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 11/3/2014 1:38:34 PM 6976 (0x1B40)
Running as user "SYSTEM" ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Detected 253651 MB free disk space on system drive. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
DetectWindowsEmbeddedFBWF() Detecting OS Version ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Client OS is not Windows XP Embedded ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Deleted file C:\Windows\ccmsetup\client.msi ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Successfully ran BITS check. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
SSL Registry key Software\Microsoft\CCM not found, assuming Client SSL is disabled. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Certificate doesn't have EKU, meaning good for all usages. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Verified file 'C:\Windows\ccmsetup\ccmsetup.cab' is MS signed. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Successfully extracted manifest file C:\Windows\ccmsetup\ccmsetup.xml from file C:\Windows\ccmsetup\ccmsetup.cab. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Loading manifest file: C:\Windows\ccmsetup\ccmsetup.xml ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Successfully loaded ccmsetup manifest file. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Couldn't get directory list for directory 'http://configmgrsrv.ad/CCM_Client/ClientPatch'. This directory may not exist. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Adding file 'http://configmgrsrv.ad:80/CCM_Client/x64/WindowsUpdateAgent30-x64.exe' to BITS job, saving as 'C:\Windows\ccmsetup\WindowsUpdateAgent30-x64.exe'. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Adding file 'http://configmgrsrv.ad:80/CCM_Client/i386/client.msi' to BITS job, saving as 'C:\Windows\ccmsetup\client.msi'. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Couldn't get directory list for directory 'http://configmgrsrv.ad/CCM_Client/i386/00000409'. This directory may not exist. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Starting BITS download for client deployment files. ccmsetup 11/3/2014 1:38:34 PM 6980 (0x1B44)
Successfully completed BITS download for client deployment files. ccmsetup 11/3/2014 1:38:35 PM 6980 (0x1B44)
Successfully downloaded client files via BITS. ccmsetup 11/3/2014 1:38:35 PM 6980 (0x1B44)
Updated security on object C:\Windows\ccmsetup\. ccmsetup 11/3/2014 1:38:35 PM 6980 (0x1B44)
Certificate doesn't have EKU, meaning good for all usages. ccmsetup 11/3/2014 1:38:35 PM 6980 (0x1B44)
Certificate doesn't have EKU, meaning good for all usages. ccmsetup 11/3/2014 1:38:35 PM 6980 (0x1B44)
Verified file 'C:\Windows\ccmsetup\WindowsUpdateAgent30-x64.exe' is MS signed. ccmsetup 11/3/2014 1:38:35 PM 6980 (0x1B44)
Installing file 'C:\Windows\ccmsetup\WindowsUpdateAgent30-x64.exe' with options '/quiet /norestart'. ccmsetup 11/3/2014 1:38:35 PM 6980 (0x1B44)
File 'C:\Windows\ccmsetup\WindowsUpdateAgent30-x64.exe' returned exit code 775. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
Finished installing file 'C:\Windows\ccmsetup\WindowsUpdateAgent30-x64.exe'. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
An MP does not exist on this machine. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
No client is currently installed. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
Installing version 4.00.6487.2000 of the client with product code {2609EDF1-34C4-4B03-B634-55F3B3BC4931} ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
MSI PROPERTIES are CCMHTTPPORT="80" CCMHTTPSPORT="443" INSTALL=ALL ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
There are no certificate(s) that meet the criteria. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
Failed in GetCertificate(...): 0x80040281
ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
File 'C:\Windows\ccmsetup\{4CD82FBB-0AFC-4864-A089-15364DF5F14B}\client.msi' doesn't have a valid digital signature. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
A Fallback Status Point has not been specified. Message with STATEID='316' will not be sent. ccmsetup 11/3/2014 1:38:39 PM 6980 (0x1B44)
Thanks,
Dom
System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Help with masking tool not working. my brush isn't making any changes and doesn't show mask overlay everything else is ok, we have reset brushes and tools uninstalled and re installed program nothing works

anyone have any idea's to fix

This forum is about the Cloud as a delivery process, not about using individual programs
If you start at the Forums Index https://forums.adobe.com/welcome
You will be able to select a forum for the specific Adobe product(s) you use
Click the "down arrow" symbol on the right (where it says All communities) to open the drop down list and scroll

SCCM 2007 package not getting installed

Dear Exprt,
I have run package to run aotumatically but its not installed
[email protected]

Try restarting the machine once. If a reboot is pending on the machine from a previous application/patch installation (via SCCM), then new installations will wait until restart.
~ Räjeésh M | Blog: ScorpITs |
Please remember to 'Mark as Answer' or 'Vote as Helpful' on the post that helps. It helps others reading the thread and recognizes useful contributions.

Right Click tools for SCCM 2007 issue

We have SCCM 2007 R2 with Right click tools installed (I know this is not a direct SCCM query but linked to it and thought I might try my luck here)
I use the "ConfigMgr Collection Tools - Add Systems to a collection" option within Right click tools a lot
However in the last few days it keeps failing a lot with the following error message
Line:68
Char: 5
Error: Object required: 'objDialogWindow.document.body'
The Addcoll.hta looks like the following
Line 68: LineobjDialogWindow.document.body.style.fontFamily = "Helvetica"
Line 69: objDialogWindow.document.body.style.fontSize = "11pt"
Line 70: objDialogWindow.document.writeln "<html><body>Adding PCs to " & collName.Value & " </body></html>"
Line 71: objDialogWindow.document.title = "Please wait."
Line 72: objDialogWindow.document.body.style.backgroundColor = "dodgerblue"
Line 73: objDialogWindow.document.body.style.borderStyle = "none"
Line 74: objDialogWindow.document.body.style.marginTop = 15
Line 75: AddToCollection ComputerList.value, CollID.value, ss.Value, objDialogWindow
Line 76: objDialogWindow.Close()
Line 77: self.ResizeTo 400,550
Has anyone had this issue and if so how have you resolved it?

You need to contact the author of the tool and get them to help out. This is not a CM07 issue.
However having said that it look like you are having a problem with the font.
http://www.enhansoft.com/

Photoshop Elements 8.0: deplovment with SCCM 2007

Hello
We are currently planning the transition to Windows 7 Enterprise.
The deployment will take place with MS SCCM 2007 - we could not find any policies regarding this case.
We need to know if Photoshop Elements 8.0 with the following client applications, SCCM and standard user-rights is running.
Used software products / local application deployed on clients:
• Microsoft Windows 7 Enterprise
• Internet Explorer 8.0
• Adobe Flash Player 10.0.32.18
• Adobe Shockwave Player 11.5.2
• Adobe Acrobat Reader 9.2
• Windows Media Player 12.0
• Microsoft Office 2007 Enterprise mit SP2
• Sun Java Runtime Environment (JRE) 6.17
• Microsoft .NET Framework 3.5
• Ghostscript 8.7
• Software-Deployment: Microsoft SCCM 2007 R2 SP2
• Server-Plattform: Microsoft Windows Server 2008R2
• Standard User-Rights
We ask for verification of requirements, whether the necessary conditions are met by PSE 8.0.
Best wishes,
Simon

Hi Simon,
I would request you to contact the Adobe Tech Support/Customer Care team and they should able to provide a confirmation on these queries.
As per my knowledge, we dont impose any explicit restrictions on PSE working with Ms SCCM 2007/Server 2008/ or with Standard User Rights.
But for installing PSE and doing a certain operations, you need to have admin rights.
Again, I would request you to get in touch with support team and get a confirmation.
Regards,
Ankush

Sccm 2007 wsus spk2 updated now missing FCS in products

I have a TESTLAB with SCCM 2007 that has been running fine and deploying Forefront Client Security. In SCCM under SUP I can see FCS in the products. I installed the kb2720211 WSUS SPK 2 update and things are doing fine. So I do the same thing
in production and upgrade to WSUS 3.0 SPK2. Then I saw where I need to install KB2734608 to be able to work with Windows 8 and 2012 SERVER from SCCM 2007. I only installed it in production not in TESTLAB, I guess I broke my rule there. a week or two
go by and I notice that the FCS definitions stopped gong to windows 7 clients. Only have one Windows 8.1 in testing right now. not deployed in Production yet.
Now I go trouble shooting and on the TESTLAB I can go to SUP and configure my Classification and PRODUCTS, I can still see FCS in the software update point component listed in products. I can also open WSUS in TESTLAB from Admin tools but I know not
to manage products from here. On Production I do not see FCS anymore, it shows Microsoft Client Protection and Forefront Endpoint Protection 2012 in the SUP Products. My question is do I continue to move forward with upgrading TESTLAB and production to
use Forefront Endpoint Protection which I have not read how to upgrade yet? Or can I just uninstall the KB 2734608 and fix FCS for now?

Again the ONLY support report is to use the CM07 restore procedures. Will everything work after your restore? Who know as there is no way to know what the problem was/is. There
will be gotcha when you restore your CM07 site and they sometime will fix themselves and other times it is just faster to force them to work. As such, I ALWAYS recommend to my clients that if they ever have to restore their CM environment that they contact
CSS directly for support. This way CSS can ensure that the site is healthy and working correctly. There is No way to do that within the forums in any meaningful way.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCCM 2007-2012 migration job

Hi,
We have an empty SCCM 2012 R2 environment (only testmachines in it).
Now I would like to migrate some first Windows 7 machines by pushing a SCCM 2012 client to it. Therefore first the collections and packages of SCCM 2007 should be migrated.
So I started an SCCM 2012 Collection migration job from SCCM 2007 to 2012:
1.Selected only the Windows 7 collections (only those should be migrated, not the XP ones)
2.selected software assigned to it (it comes from a DFS-share \\ourcompany\share
3.all with default values, except "Enable programs for deployment"
My questions:
1.It took only 10 minutes to complete (share is 100 GB) but I see now software is not distributed to distribution point.
=> Is that normal? Should I run distribute to distribution point for all packages are rerun migration job with differen values?
2.After step 1, I can now migrate a Windows 7 computer fro SCCM 2007 to 2012, right?
Everything looks fine to me. There is also the object migration but don't think I need it.Just want to doublecheck.
Please advise.
J.
Jan Hoedt

#1: that's default behavior. Packages are migrated, but not distributed to DPs automatically. That's up to you right now.
#2: yes, but that's independent from step #1. You can install the CM12 client to the clients anytime.
Torsten Meringer | http://www.mssccmfaq.de

Office 2013 SP1 fails with code 17302 - SCCM 2007 R2

Hi,
I am trying to deploy Office 2013, along with SP1, in the following order:
1. Prompt to close all office apps and continue (vbs)
2. Installation of Office 2013, using modified msp.
3. Restart
4. Installation of SP1 with command line /passive /norestart.
I am doing this all through a package I created in SCCM 2007 R2.
The first few programs works well. However, when the installation of SP1 starts, SCCM launches the program, then SP1 fails with code 17302.
Manual installation, through command prompt, with the same switches works fine.
The error is only when remotely deploying.
The system is Windows 7 X86 with latest SP.
Please help!

Hi,
Have you checked the log file? Does it say anything there? Also, where is the SP1 installation file stored? Since this only happens while remotely deploying, check the network or the setting of your filewall.
By the way, you can slipstream Service Pack 1 with your Office 2013 installation media, Office 2013 will be directly installed at Service Pack 1 level, saving you the trouble of applying it afterwards. For the details, please refer to this article:
http://www.howto-outlook.com/otherprograms/slipstreamoffice2013sp.htm
(Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.)
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Uninstalling programs using sccm 2007 sp3

Hi there,
We have imaged 300 desktops which have office 2007 preinstalled. What we want to do is uninstall office using sccm 2007....my questions is that is this path possible?? Big question is can we uninstall a program that has not been deployed with
SCCM???

Hi,
this is an example for MS Visio 2007 Professional but it is valid for all apps like Visio, Project, Office (2007 and 2010 Versions). The only difference is in the <Configuration Product="APPLICATION ID">
line
<Configuration Product="VisPro">
<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
<Setting Id="SETUP_REBOOT" Value="Never" />
</Configuration>
This line in SilentUninstallConfig.xml file stops the client from restarting after an uninstall procedure.

Hi, I just installed my Creative Suite 6 and the programs close right after launching (for about 5 seconds) with no dialog box about an error. I have tried uninstalling and re-installing but still the same thing. Help pls!

Hi, I just installed my Creative Suite 6 and the programs close right after launching (for about 5 seconds) with no dialog box about an error. I have tried uninstalling and re-installing but still the same thing. Help pls!

Sign in, activation, or connection errors | CS5.5 and later
Mylenium

Users with Administrator rights not being allowed to install programs.

I have 3 users in my office that are not able to download and install programs due to a security prompt that says that they are unable to install the program due to not having administrator rights. But in the users menu the user accounts are setup with
full administrator rights. Is this a common problem?

Hi,
Are they domain administrator or local administrator? Is there any group policy restriction?
Please refer to this similar thread:
http://answers.microsoft.com/en-us/windows/forum/windows_7-desktop/unable-to-install-program-and-getting-error-do-not/cd28bdae-ae0c-4dcc-96cb-00fb2490dd24
Karen Hu
TechNet Community Support

For Your Consideration: Ultimate Lync 2010 client install with SCCM 2007

While the subject of my post may be very presumptuous, I submit the following for your consideration to answer the often-asked question about how to deploy Lync 2010 client with SCCM.
Background:
I cannot understand why Microsoft made the Lync install so darned confusing, complex, and convoluted.
After our Lync 2010 FE server was up and running and all users migrated off our OCS server to the Lync environment, I spent about a month and a half trying to figure out how to:
1. Uninstall the OCS 2007 R2 client
2. Install all prerequisites for the Lync client
3. Install Lync on all user workstations silently.
While researching this, the simple answer I kept seeing given to this question was, "just use the .exe with the right switches according to the TechNet article here: http://technet.microsoft.com/en-us/library/gg425733.aspx". Well, my response is, I
tried that and while the program installed itself correctly pushed through SCCM, because I was doing it using an administrative account (i.e. the SYSTEM account) due to our users not having admin rights, when the install was done, Lync would automatically
start up, but in the SYSTEM context so that the user couldn't see it was running, they go to run it and it won't run for them. I was unable to find any switch or option to prevent the automatic launch. I suppose the simple solution to that would
be to have the user reboot, but that's unnecessarily disruptive and was contrary to the desire to make this a silent install.
The next simplest answer I saw was, "extract the MSI and use that with the right switches". Problem with that is that the MSI by itself doesn't remove the OCS client or install the prerequisites, and also either requires a registry change to even allow
the MSI to be used or a hacked MSI that bypasses the registry key check. I tried to put a package together to uninstall OCS, install the prereqs, and use a hacked MSI, but I never could get the MSI hacked properly. The other problem I ran into
was detecting if the OCS client was running in a predictable way so I could terminate it, properly uninstall it, and then do the rest of the installations. It was this problem that ultimately led me to the solution that I'm about to detail and that has
worked marvellously for us.
Solution:
As I said before, when I first looked at this problem, I started by building a typical software deployment package (Computer Management -> Software Distribution -> Packages) and then created the programs to do the install. My first attempt was
just with the .exe file provided as-is by Microsoft using the switches they document in the link above for IT-Managed Installation of Lync, and...well, the end result wasn't quite as desirable as hoped. So, my next attempt was to extract all the prerequisite
files and the Lync install MSI (both for x86 and x64), attempt to hack it to get around the "UseMSIForLyncInstallation" registry key, and make the command-lines to terminate OCS and uninstall it.
In the past when I had an install to do with SCCM that also required uninstalling an older version of a given application, I typically used the program-chaining technique. That's where you have, for example, 3 or more programs that run in a package
in a sequence and you have Program 3 be set to run after Program 2 does and then set Program 2 to run after Program 1 so you get the desired sequence of Programs 1-2-3 running in that order. So, I created programs to 1) kill Communicator.exe 2) uninstall
Communicator 2007 R2 by doing an "msiexec /uninstall {GUID}" 3) install Silverlight 4) install Visual C++ x86 5) optionally install Visual C++ x64, and then 6) install the Lync x86 or x64 client. That final step was always the point of failure because
I couldn't get the hacked MSI for the Lync Client install to work. I also realized that if Communicator wasn't running when the deployment started, that step would fail and cause the whole process to bail out with an error. That's one of the downsides
of program-chaining, if one step fails, SCCM completely bails on the deployment. This is what also led me to the key to my solution: TASK SEQUENCES.
I'm not sure how many people out there look in the "Operating System Deployment" area of SCCM 2007 where Task Sequences normally live, but I also wonder how many people realize that Task Sequences can be used for more than just Operating System deployments.
One of the biggest advantages of a task sequence is you can set a step to ignore an error condition, such as if you try to terminate a process that isn't running. Another advantage is that task sequences have some very good built-in conditionals that
you can apply to steps, for example, having the sequence skip a step if a certain application (or specific version of an application) is not installed on the machine. Both of those advantages factor highly into my solution.
OK, for those who already think this is "TL;DR", here's the step-by-step of how to do this:
First, you need to extract all the files from the LyncSetup.exe for your needed architectures. We have a mix of Windows XP and Windows 7 64-bit, so my solution here will take both possibilities into account. To extract the files, just start up
the .exe like you're going to install it, but then when the first dialog comes up, navigate to "%programfiles%\OCSetup" and copy everything there to a new location. The main files you need are: Silverlight.exe, vcredist.exe (the x64 LyncSetup.exe includes
both x86 and x64 Visual C++ runtimes, you need them both, just rename them to differentiate), and Lync.msi (this also comes in an x86 and x64 flavor, so if you have a mix of architectures in your environment, get both and either put them into their own directories
or rename them to reflect the architecture).
For my setup, I extracted the files for the x86 and x64 clients and just dumped them each into directories named after the architectures.
Next, move these files into a directory to your SCCM file server, whatever it might be that you deploy from, in our case, it was just another volume on our central site server. Go to the SCCM console into Computer Management -> Software Distribution
-> Packages and then create a new package, call it something meaningful, and then point to the directory on your SCCM file server for the source files.
Now you need to create 3 to 5 programs inside the package:
1. Name: Silverlight
   Command Line: x86\Silverlight.exe /q     (remember, inside my main Lync install folder on my distribution point, I have an x86 directory for the files from the x86 installer and an x64 folder for the files from the x64 installer.
The fact is the Silverlight installer is the same in both, so you only need one of them.)
   On the Environment tab: Program can run whether or not a user is logged in, runs with administrative rights, Runs with UNC name
   On the Advanced tab: Suppress program notifications
   All other options leave default.
2. Name: Visual C++ x86
    Command Line: x86\vcredist_x86.exe /q
   On the Requirements tab: Click the radio button next to "This program can run only on specified client platforms:" and then check off the desired x86 clients.
   Environment and Advanced tabs: same as Silverlight
   (If you have only x64 clients in your environment, change all x86 references to x64. If you have a mixed environment, create another program identical to this one, replacing references to x86 with x64.)
3. Name: Lync x86
    Command Line: msiexec /qn /i x86\Lync.msi OCSETUPDIR="C:\Program Files\Microsoft Lync" (The OCSETUPDIR fixes the issue with the Lync client wanting to "reinstall" itself every time it starts up)
    Requirements, Environment, and Advanced tabs: Same as with Visual C++ and Silverlight
    (Same deal as above if you have all x64 clients or a mix, either change this program to reflect or make a second program if necessary)
Now you need to make the Task Sequence. Go to Computer Management -> Operating System Deployment -> Task Sequences. Under the Actions pane, click New -> Task Sequence. In the Create a New Task Sequence dialog, choose "create a
new custom task sequence", Next, enter a meaningful name for the task sequence like "Install Microsoft Lync", Next, Next, Close.
The task sequence will have up to 12 steps in it. I'll break the steps down into 3 phases, the prereqs phase, uninstall OCS phase, and then Lync install phase.
Prereqs Phase:
These are the easiest of the steps to do. Highlight the task sequence and then in the Actions pane, click Edit.
1. Click Add -> General -> Install Software. Name: "Install Microsoft Silverlight". Select "Install a single application", browse to the Lync package created earlier and then select the Silverlight program.
2. Add -> General -> Install Software. Name: "Install Microsoft Visual C++ 2008 x86". Install Single Application, browse to the Lync package, select the Visual C++ x86 package.
As before, if you're an all-x64 environment, replace the x86 references with x64. If you have a mixed environment, repeat step 2, replacing x86 with x64.
3. Add -> General -> Run Command Line. Name: "Enable Lync Installation". This step gets around the UseMSIForLyncInstallation registry requirement. The Lync client MSI simply looks for the presence of this key when it runs, so
we'll inject it into the registry now and it doesn't require a reboot or anything. It just has to be there before the client MSI starts.
Command Line: reg add "hklm\Software\Policies\Microsoft\Communicator" /v UseMSIForLyncInstallation /t REG_DWORD /d 1 /f
Uninstall OCS Phase:
This part consists of up to 6 Run Command Line steps. (Add -> General -> Run Command Line)
4. Name: "Terminate Communicator". Command Line: "taskkill /f /im communicator.exe". On the Options page, check the box next to "Continue on error". This will terminate the Communicator process if it's running, and if it's not, it'll
ignore the error.
5. Name: "Terminate Outlook". Command Line: "taskkill /f /im OUTLOOK.exe". Check the "Continue on error" on the Options page here too. Communicator 2007 hooks into Outlook, so if you don't kill Outlook, it might prompt for a reboot
because components are in use.
(NOTE: If necessary, you could also add another step that terminates Internet Explorer because Communicator does hook into IE and without killing IE, it might require a restart after uninstalling Communicator in the next steps. I didn't run into
this in my environment, though. Just repeat step 5, but replace OUTLOOK.EXE with IEXPLORE.EXE)
6. Name: "Uninstall Microsoft Office Communicator 2007". Command Line: "msiexec.exe /qn /uninstall {E5BA0430-919F-46DD-B656-0796F8A5ADFF} /norestart" On the Options page: Add Condition -> Installed Software -> Browse to the
Office Communicator 2007 non-R2 MSI -> select "Match this specific product (Product Code and Upgrade Code)".
7. Name: "Uninstall Microsoft Office Communicator 2007 R2". Command Line: "msiexec.exe /qn /uninstall {0D1CBBB9-F4A8-45B6-95E7-202BA61D7AF4} /norestart". On the Options page: Add Condition -> Installed Software ->
Browse to the Office Communicator 2007 R2 MSI -> select "Match any version of this product (Upgrade Code Only)".
SIDEBAR
OK, I need to stop here and explain steps 6 and 7 in more detail because it was a gotcha that bit me after I'd already started deploying Lync with this task sequence. I found out after I'd been deploying for a while that a tech in one of our remote
offices was reinstalling machines and putting the Communicator 2007 non-R2 client on instead of the R2 client, and my task sequence was expecting R2, mostly because I thought we didn't have any non-R2 clients out there. So, at first I just had our Help
Desk people do those installs manually, but later on decided to add support for this possibility into my task sequence. Now, when you normally uninstall something with msiexec, you would use the Product Code GUID in the command, as you see in steps 6
and 7. All applications have a Product Code that's unique to a specific version of an application, but applications also have an Upgrade Code GUID that is unique for an application but common across versions. This is part of how Windows knows that
Application X version 1.2 is an upgrade to Application X version 1.1, i.e. Application X would have a common Upgrade Code, but the Product Code would differ between versions 1.1 and 1.2.
The complication comes in that Communicator 2007 and Communicator 2007 R2 have a common Upgrade Code, but different Product Codes and the "MSIEXEC /uninstall" command uses the Product Code, not the Upgrade Code. This means that if I didn't have step
6 to catch the non-R2 clients, step 7 would be fine for the R2 clients, but fail on non-R2 clients because the Product Code in the MSIEXEC command would be wrong. Luckily, we only had one version of the non-R2 client to deal with versus 4 or 5 versions
of the R2 client. So, I put the command to remove Communicator 2007 non-R2 first and checked for that specific product and version on the machine. If it was present, it uninstalled it and then skipped over the R2 step. If non-R2 was not present,
it skipped that step and instead uninstalled any version of the R2 client. It's important that steps 6 and 7 are in the order they are because if you swap them, then you'd have the same outcome as if step 6 wasn't there. What if neither is on the
machine? Well the collection this was targeted to included only machines with any version of Communicator 2007 installed, so this was not a problem. It was assumed that the machines had some version of Communicator on them.
8. Name: "Uninstall Conferencing Add-In for Outlook". Command Line: "msiexec.exe /qn /uninstall {730000A1-6206-4597-966F-953827FC40F7} /norestart". Check the "Continue on error" on the Options Page and then Add Condition ->
Installed Software -> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
9. Name: "Uninstall Live Meeting 2007". Command Line: "msiexec.exe /qn /uninstall {69CEBEF8-52AA-4436-A3C9-684AF57B0307} /norestart". Check the "Continue on error" on the Options Page and then Add Condition -> Installed Software
-> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
Install Lync phase:
Now, finally the main event, and it's pretty simple:
10. Click Add -> General -> Install Software. Name: "Install Microsoft Lync 2010 x86". Select "Install a single application", browse to the Lync package created earlier and then select the "Lync x86" program. As before, if you
only have x64 in your environment, replace the x86 with x64, or if you have a mixed environment, copy this step, replacing x86 references with x64.
And the task sequence is done! The final thing you need to do now is highlight the task, click Advertise in the Actions pane, and deploy it to a collection like you would with any other software distribution advertisement. Go get a beer!
Some final notes to keep in mind:
1. You can't make a task sequence totally silent...easily. Users will get balloon notifications that an application is available to install. The notifications cannot be suppressed through the GUI. I've found scripts that supposedly
hack the advertisement to make it be silent, but neither of them worked for me. It was OK, though because in the end we wanted users, especially laptop users, to be able to pick a convenient time to do the upgrade. The task sequence will appear
in the "Add/Remove Programs" or "Programs and Features" Control Panel. You can still do mandatory assignments to force the install to happen, you just can't make it totally silent. On the plus side, the user shouldn't have to reboot at any point
during or after the install!
2. In the advertisement setup, you can optionally show the task sequence progress. I've configured the individual installs in this process to be silent, however, I did show the user the task sequence progress. This means instead of seeing
5 or 6 Installer windows pop up and go away, the user will have a single progress bar with the name of the step that is executing.
3. One step that I didn't consider when I actually did this was starting the Lync client as the user when the install was complete. The user either had to start the client manually or just let it start on its own at the next logon. However,
while I was writing this, I realized that I could possibly start the client after installing by making another Program in the Lync Package with a command line that was along the lines of "%programfiles%\Microsoft Lync\communicator.exe" and then in the Environment
tab, set it to "Run with user's rights" "only when a user is logged on".
4. My first revision of this task sequence has the Prereqs phase happening after the OCS uninstall phase, but I kept running into problems where the Silverlight installer would throw some bizarre error that it couldn't open a window or something wacky
and it would fail. Problem was, I couldn't re-run the task sequence because now it would fail because OCS had been uninstalled, so that's why the Prereqs happen first. It ran much more reliably this way.
5. For some reason that baffles me, when I'd check the logs on the Site Server to monitor the deployment, I'd frequently see situations where the task sequence would start on a given machine, complete successfully, almost immediately start again, and
then fail. I'm not sure what is causing that, but I suspect either users are going to Add/Remove Programs and double-clicking the Add button to start the install instead of just single-clicking it, or the notification that they have software to install
doesn't go away immediately or Lync doesn't start up right after the install, so they think the first time it didn't take and try it a second time.
I hope this helps some of you SCCM and Lync admins out there!

On Step 8 I found multiple product codes for the Conferencing Add-In for Outlook. Here's a list of the ones I found in the machines on my network:
{987CAEDE-EB67-4D5A-B0C0-AE0640A17B5F}
{2BB9B2F5-79E7-4220-B903-22E849100547}
{13BEAC7C-69C1-4A9E-89A3-D5F311DE2B69}
{C5586971-E3A9-432A-93B7-D1D0EF076764}
I'm sure there's others one, just be mindful that this add-in will have numerous product codes.

SCEP install and policy issue (after migration SCCM 2007 to 2012)

Hi,
We have some terminal services which were connected to SCCM 2007.
I migrated 3 of them (via "install client" in SCCM 2012), what worked fine. Since they become member of the Windows server group + terminal services group, they get the scep-client as well as a specific policy.
Now we have 1 terminal server which did not install the scep client.
Logfile:
Failed to get EP event code under registry key SOFTWARE\Microsoft\CCM\EPAgent   EndpointProtectionAgent   21/08/2014 11:19:42   43640 (0xAA78)
Failed to get EP event message under registry key SOFTWARE\Microsoft\CCM\EPAgent   EndpointProtectionAgent   21/08/2014 11:19:42   43640 (0xAA78)
State 1, error code 0 and detail message are not changed, skip updating registry value   EndpointProtectionAgent   21/08/2014 11:19:42   43640 (0xAA78)
File C:\Windows\ccmsetup\SCEPInstall.exe version is 4.5.216.0.   EndpointProtectionAgent   21/08/2014 11:19:42   43640 (0xAA78)
Sleep 10 seconds and retry read ProductName of the AM solution   EndpointProtectionAgent   21/08/2014 11:19:42   43640 (0xAA78)
Sleep 10 seconds and retry read ProductName of the AM solution   EndpointProtectionAgent   21/08/2014 11:19:52   43640 (0xAA78)
Sleep 10 seconds and retry read ProductName of the AM solution   EndpointProtectionAgent   21/08/2014 11:20:02   43640 (0xAA78)
Sleep 10 seconds and retry read ProductName of the AM solution   EndpointProtectionAgent   21/08/2014 11:20:12   43640 (0xAA78)
Sleep 10 seconds and retry read ProductName of the AM solution   EndpointProtectionAgent   21/08/2014 11:20:22   43640 (0xAA78)
Unable to query registry value (ProductName), return (0x80070002) means EP client is NOT installed successfully.   EndpointProtectionAgent   21/08/2014 11:20:32   43640 (0xAA78)
So I installed the client manually via "SCEPInstall.exe /policy z:\client\ep_defaultpolicy.xml" (after a pushd \\sccmserver\c$\...client\).
2 things:
1.any idea why it wouldn't install "failed to get EP event code under reigstry key" ..?
2.specific scep terminal server policy will be applied afterwards (file exclusions etc), right (don't see it yet and refreshed policy several times)?
J.
Jan Hoedt

Hi,
I have seen a temporary solution, created a package with the command line: REG add “HKLM\SOFTWARE\Microsoft\Microsoft Security Client” and deployed this program to the Client.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Unable to install BR&E Promax license on a SCCM 2007 R2 client

Unable to install BR&E Promax license on a SCCM 2007 R2 client
in Execmgr log could see below entries,
Program exit code -1073741510 in execmgr
Script for Package:xxxxxx, Program: Install failed with exit code 3221225786

Unable to install BR&E Promax license on a SCCM 2007 R2 client
in Execmgr log could see below entries,
Program exit code -1073741510 in execmgr
Script for Package:xxxxxx, Program: Install failed with exit code 3221225786
That error code is from BR&E Promax and not from CM07. You need to contact them to find out what it means.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCCM 2007 - Uninstall user rights installed program

Similar Messages

Maybe you are looking for