SCCM 2007 console client=no,Approved= Approved,there is further information

Hi Team,
We are having parent and child Domain. Consider ABC is Parent where SCCM Installed and XYZ is the Child Domain.
Machines in the Child dmain are not publishing AD information to the parent Domain.
Client : Automatic Discovery was unsuccessful. Also, in the console under Client = NO.
Kindly let us know the solution.
\Arjun Kandasamy

Hi Jason,
Location services Log: LSGetVersionFRomAD : failed to retrieve version of the site 'XYZ' (0x80004005)
we have check the firewall, and current settings provided below,
From SCCM serverto client on 3268/TCP is allowed in the firewall.
From Client to SCCM server on port 3268 /TCP is not allowed in the firewall.
Kindly let me know, why the clients in the child domain not publishing AD Information.
\Arjun Kandasamy

Similar Messages

SCCM 2012 clients in SCCM 2007 console

Hi
If a Windows 7 system has sccm 2012 client installed, will it get discovered in SCCm 2007 console.
Regards Sushain KApoor

If you enable AD discovery to this client, the client object will be discovered. Anyway, the SCCM 2012 clients cannot be managed by SCCM 2007. See below.
Configuration Manager also checks that you have assigned the Configuration Manager 2012 client to a site that supports the Configuration Manager client version. If you have used automatic site assignment and the client is assigned to a Configuration Manager
2007 site, the client automatically tries to find a Microsoft System Center Configuration Manager 2012 site. It first checks Active Directory Domain Services and if this is not successful (for example, the Active Directory schema is not extended or the computer
is a workgroup client), the client then checks for site information from its assigned management point. However, if the client was assigned with a specific site code and assigns to a Configuration Manager 2007 site, site assignment fails and you must manually
reassign the client to a Microsoft System Center Configuration Manager 2012 site.
Juke Chou
TechNet Community Support

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

Patches not visible in SCCM 2007 Site server even after approving the patches in WSUS

Hi,
The patches are not appearing in SCCM 2007 site server after approving the same patches in WSUS.
Below are the patches.
MS14-080: Cumulative Security Update for Internet Explorer - Windows Server 2008 SP2 - IE 7 - KB3008923 [23,186.1]
MS14-018: Cumulative Security Update for Internet Explorer - IE 11 - KB2929437 - Windows Server 2008 R2 SP1 (x64) [4,32.4]
MS14-066: Vulnerability in Schannel Could Allow Remote Code Execution - Windows Server 2008 SP2 - KB2992611 (x64) - V2 [1,8.3]
MS14-038: Vulnerability in Windows Journal Could Allow Remote Code Execution - Windows Server 2008 SP2 - KB2971850 [1,8.1]
MS09-060: Vulnerabilities in Microsoft Active Template Library (ATL) ActiveX Controls for Microsoft Office Could Allow Remote Code Execution - Visio Viewer 2007 SP1/SP2 [1,8.1]
MS12-001: Vulnerability in Windows Kernel Could Allow Security Feature Bypass - Windows Server 2008 R2 Gold (x64) [1,8.1]
MS14-033: Vulnerability in Microsoft XML Core Services Could Allow Information Disclosure - Windows Server 2008 SP2 - KB2939576 [1,8.1]
MS14-025: Vulnerability in Group Policy Preferences Could Allow Elevation of Privilege - Windows Server 2008 SP2 - KB2928120 (x64) [1,7.8]
MS13-014: Vulnerability in NFS Server Could Allow Denial of Service - Windows Server 2008 R2 Gold/SP1 (x64) [1,7.7]
I have approved the above patches in WSUS and ran syncronization. The log wsyncmgr.log show that synchronization is done and even all child sites are syncronized. But I am unable to find the above even in the parent site. Checked all the SUP settings and
all the 2008 server updates are set and marked to download.
Please help me out on fixing this.

So you should NEVER approve anything in WSUS. This will cause problems with your clients. Honestly since you approved things in WSUS, I would uninstall WSUS and reinstall it, reinstall the SUP, this will clear up any issues that now exist.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCCM 2007 - All clients from primary site have vanished from central site collections

Hi all,
we have a SCCM 2007 R2 setup with one central site, one Primary Site (A) with a secondary site hanging off it and another Primary Site (B). Suddenly all the clients from the Primary Site A (and also it's Secondary Site) have vanished from the central
site. All the clients are still present when we check Collections from the admin console on Primary Site A site server - they have simply disappeared when we check Collections from the Central Site admin console.
Can anyone provide any info on a good starting point for troubleshooting this issue? As a sidenote, we can still push packages out to the Primary Site A distribution point and both the Primary and Central site can communicate/ping each other.
Any help/info would be much appreciated!
Thanks

Check the
site replication on central site, is that SQL is working fine, and also see the
inbox folder in central site, might be there is backlog and those DDR files are
not processing, and after maintenance they got deleted.<o:p></o:p>
please run
the heartbeat discovery by hour or day, and once the clients will sent all the
DDR files then they will appears again.<o:p></o:p>
Sharad Singh | My blogs: SharadTech | Twitter:
@SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.

SCCM 2007 migrated clients (SCCM 2012) are still visible

Hi,
We migrated some SCCM 2007 Windows 7 clients to SCCM 2012 (upgraded the clients via push).
This worked fine for most of the clients but not all so I cannot just delete clients from SCCM 2007.
How can we clean the succesfully migrated? I cannot see which ones are succesfully migrated in SCCM 2007, the all show active (even the succesfully migrated ones).
Pls advise.
J.
Jan Hoedt

The client will become inactive if it's not requesting client policies, sending heartbeats, sending inventories, or sending status messages any more in a period of by default 7 days (but it all depends on the configured intervals). Also, if you
delete clients that are still active, they will come back with the next heartbeat if they are still active.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SCCM 2007 Console

Team,
I am trying to install SCCM 2007 SP2 console in Windows 8 system its giving the fallowing error. Please help me in resolving this
Site database Connection Failed.
Regards,
Raghavendra

Team,
I am trying to install SCCM 2007 SP2 console on Windows 8 system its giving the fallowing error. Please help me in resolving this
Site database Connection Failed.
Regards,
Raghavendra

OSD: upgrade sccm 2007 (XP) client to 2012, then deploy TS

Hi,
We have some Windows XP machines in our SCCM 2007. They are discovered via AD in SCCM 2012.
Now we would like to upgrade their client to SCCM 2012 then deploy (available) a task sequence to it (Windows 7 install). This way users can choose whenever to upgrade to Windows 7.
My questions:
*When I right click an XP/SCCM 2007 client and choose upgrade, nothing happens. How can I troubleshoot/follow the upgrade?
*Should the task sequence (SCCM MDT) contain a particular step or can we use the same as a bare metal (PXE) deploy (we do not want to keep any data from the pc)?
Please advise,
J.
Jan Hoedt

Do I understand it correct, that you are trying a Client Push Installation? If so, then start with looking at the ccm.log on the server-side for errors. That log file contains all the information about the push action.
You should be able to use the same task sequence. Just check the deployment settings and the first action of the task sequence (make sure it restarts in WinPE).
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SCN Content Submission: Is there any further information on the submission status?

Hi colleagues,
I understand and have read a couple of times that I can contribute content via the content submission (SAML Response from SAP ID Service).
and I see the status "Submitted" for my document.
The question is, is there a way to get more information about the current status of the submitted document? Or is the only information I get the mail "don't call us, we'll call you" , i.e. the automatically generated mail telling me that I'll be informed once the content is published and and that I'll receive a link to the published document?
Cheers,
Jasmin

Hi Jasmin,
You can contact the content team directly at [email protected] to determine the status of your submission.
fyi - After it has been published, you will receive an automatic eMail with the URL.
Jason

SCCM 2007 to SCCM 2012 client migration via Powershell

Hi
I'm looking for a controlled way to migrate a SCCM 2007 server client to SCCM 2012. A push of SCCM Console is no option.
I 'll do all the testing but hoped to gain some time by having these questions answered:
*can an install of SCCM 2012 client be remotely triggered in one go (no uninstall of 2007 needed)?
*if uninstall is needed (of sccm 2007 client), does it need a reboot?
What command to use (preferrably powershell):
\\ourserver\Client\ccmsetup.exe" -argumentlist "SMSSITECODE=sitecode","SMSMP=oursccmserver","SMSCACHESIZE=8000","FSP=oursccmserver","CCMLOGMAXSIZE=104857600"
OR (guess that's the command SCCM is using)
Install-CMClient-DeviceName$ComputerName-IncludeDomainController$False-SiteCodePRD-ForceReinstall$True-AlwaysInstallClient$True-Verbose
J.
Jan Hoedt

do I need to import the machine in SCCM 2012 also or launching the SCCM 2012 install from a SCCM 2007
will do this?
How will you do that? This does not work at all when using client push obviously. You can only use packages/programs to update clients to CM12 in that case and that's something you did not want to do.
Torsten Meringer | http://www.mssccmfaq.de

SCCM 2007 client not install

Dear Exprt,
Please assist me to install client, this my first setup i had followed all guide line but could not success.
in SCCM admin console client discover but client not getting install according to log error i had follow some internet provided steps however still not success, i dont know were i made mistake for server installation.
Kind request for your usual support...
In text:
<![LOG[MPs:]LOG]!><time="05:59:35.906+-180" date="02-03-2014" component="ccmsetup" context="" type="1" thread="2128" file="ccmsetup.cpp:4527">
<![LOG[ SCCMSRV.SCCM-AD.COM]LOG]!><time="05:59:35.906+-180" date="02-03-2014" component="ccmsetup" context=""
type="1" thread="2128" file="ccmsetup.cpp:4542">
<![LOG[Updated security on object C:\Windows\system32\ccmsetup\.]LOG]!><time="05:59:35.906+-180" date="02-03-2014" component="ccmsetup" context="" type="0" thread="2128" file="ccmsetup.cpp:8849">
<![LOG[Sending Fallback Status Point message, STATEID='100'.]LOG]!><time="05:59:35.906+-180" date="02-03-2014" component="ccmsetup" context="" type="1" thread="2128" file="ccmsetup.cpp:9326">
<![LOG[State message with TopicType 800 and TopicId {3F0B6515-0505-4DF2-881C-F4A358589302} has been sent to the FSP]LOG]!><time="05:59:36.183+-180" date="02-03-2014" component="FSPStateMessage" context=""
type="1" thread="2128" file="fsputillib.cpp:730">
<![LOG[Running as user "SYSTEM"]LOG]!><time="05:59:36.183+-180" date="02-03-2014" component="ccmsetup" context="" type="1" thread="4004" file="ccmsetup.cpp:2690">
<![LOG[Detected 53138 MB free disk space on system drive.]LOG]!><time="05:59:36.183+-180" date="02-03-2014" component="ccmsetup" context="" type="1" thread="4004" file="ccmsetup.cpp:463">
<![LOG[DetectWindowsEmbeddedFBWF() Detecting OS Version]LOG]!><time="05:59:36.183+-180" date="02-03-2014" component="ccmsetup" context="" type="1" thread="4004" file="ccmsetup.cpp:509">
<![LOG[Client OS Version is 6.1, Service Pack Version 0]LOG]!><time="05:59:36.183+-180" date="02-03-2014" component="ccmsetup" context="" type="1" thread="4004" file="ccmsetup.cpp:533">
<![LOG[Client OS is not a supported Windows Embedded Platform]LOG]!><time="05:59:36.183+-180" date="02-03-2014" component="ccmsetup" context="" type="1" thread="4004" file="ccmsetup.cpp:535">
<![LOG[Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again.]LOG]!><time="05:59:36.183+-180" date="02-03-2014" component="ccmsetup" context=""
type="1" thread="4004" file="ccmsetup.cpp:2774">
<![LOG[Successfully ran BITS check.]LOG]!><time="05:59:36.937+-180" date="02-03-2014" component="ccmsetup" context="" type="1" thread="4004" file="ccmsetup.cpp:7105">
<![LOG[Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 404)]LOG]!><time="05:59:36.968+-180" date="02-03-2014" component="ccmsetup" context="" type="3" thread="4004"
file="ccmsetup.cpp:5969">
<![LOG[Sending Fallback Status Point message, STATEID='308'.]LOG]!><time="05:59:36.968+-180" date="02-03-2014" component="ccmsetup" context="" type="1" thread="4004" file="ccmsetup.cpp:9326">
<![LOG[State message with TopicType 800 and TopicId {BED7FDFE-DBD7-48F5-853A-A81A87AEED84} has been sent to the FSP]LOG]!><time="05:59:36.984+-180" date="02-03-2014" component="FSPStateMessage" context=""
type="1" thread="4004" file="fsputillib.cpp:730">
[email protected]

"Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 404)"
Is you MP healthy? Based on this message, it is not.
Jason | http://blog.configmgrftw.com

SCCM 2007 R3 installation now showing in 'About SCCM..'

Hello. I ve succesfuly installed R2 and R3 for SCCM 2007 console and i can see them in the Controll Panel, but when i look up the About section of the console it does not show sp installed. Also it is missing some options we have in 2007 R3, e.g.
a few options missing when right clicking a collection, im assuming they were added with the sp's.
Thank you for any info.

Go to below path and verify the Version, Build Number and R2 or R3 installation status.
SCCM Console->Site Database->Site Management
Right Click Site name,
Click on Properties.

After migration from sccm 2007, there are many systems with no client installed

Hi Everyone,
We have migrated our environment from SCCM 2007 to SCCM 2012 , And Manual client push installation has been done by HeadQuarter SCCM admins on site code of our region.
But as i see , in all systems collection based on OU, there are approx 50% systems with no client installed.
There may be some stale systems in AD.
Is there any way so that i can list out all Stale or old computers which are not in use anymore records of systems from Active directory and so that i move them to OU for which system discovery is not enabled.
Also, it will very useful if i get more information on lastLogonTimeStamp and such more properties which specifies system as stale or OFF the network for some period..

You could also remove the objects without a client and adjust the settings in the
Options tab of the Active Directory System Discovery Properties. By tweaking those options you can make sure that you're not discovering those old objects in the first place.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

WSUS Server settings and Migrating SCCM 2007 Clients to SCCM 2012 R2

I am in the process of migrating a site from SCCM 2007 to SCCM 2012 R2.
Whilst doing this I came across the following issue:
The first issue is the workstations are woefully out of date, patch and update-wise, some have never had a patch applied as the branch IT staff are building them from the original disk. The policy is set in the SCCM 2007 client to point the machines at
the 2007 WSUS server, which is not set to deliver any updates to 2007 clients and hasn't been for a while. So as soon as the client is installed they lose the ability to get updates from Microsoft and don't get them from the 2007 WSUS server either.
Issue number 2 is the machines are a mixture of hand-built machines to SCCM 2007 delivered images, the SCCM image is patch using offline patching so they are somewhat up-to-date, but the hand-built machines are not and as there is no standardization on
the Microsoft Update client settings, the IT person on-site sets it to whatever he/she feels like, as it makes no difference once the client is installed and the policy applied.
So, when I come to update the client from 2007 to 2012, the following occurs
The Client uninstalls, and the GPO policy settings for Windows Update are removed.
Depending on the setup of the client initially, some machines are then going to Microsoft for their updates (literally 100s) and although the new client is installed the policy update does not fire to update the Windows Update Policy settings, sometimes
for hours after the install finishes. My thoughts are that it just can't run the policy as it is bogged down by patches updating and, in some cases, rebooting and then updating some more.
As a workaround I have had to go in an physically disable Microsoft Update on these machines, which stops the downloading and eventually allows the policy to apply, after which the machine then begins to receive patches from WSUS in a controlled method during
maintenance windows.
I have tried a number of approaches, even setting the Global Group Policy for Windows Update, but the install still removes the keys and basically sets Windows updates back to whatever it was set before the policy was applied and stays that way until the
new client is installed and the Machine policy reapplied. This can be speeded up by initiating it on the client obviously, but that would mean going to each client or using right-click tools on each machine, which is not an option.
What I would like to know is if there is something I am missing from my methods or is it just that I have never been on a site with such out of date workstations built in such different ways.
Any help would be appreciated.

First note that clients do *not* get updates from WSUS in ConfigMgr. The Windows Update Agent (WUA) must point to the WSUS integrated into ConfigMgr (by virtue of having the SUP installed on it) but this is only to make the update catalog/metadata available
to it. Approving updates in WSUS is unsupported for ConfigMgr.
What you've described above is all working as designed although these clients are falling into a gap between the 2007 and 2012 configuration and thus they are reaching out to Windows Update during this gap and installing updates. To prevent this, you
need to disable automatic updates via a domain group policy. This will prevent all automated WUA activity including installing updates from any source automatically. This will not interfere with ConfigMgr Software Updates in any way though.
Jason | http://blog.configmgrftw.com | @jasonsandys

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.

SCCM 2007 console client=no,Approved= Approved,there is further information

Similar Messages

Maybe you are looking for