SCCM 2007 genarating duplicate client entry becuase of Same Hardware ID

Could any one explaine what is this hardware ID in sccm for client machine
How hardware ID is changing for same machine ?
where we can see hardware in machine ?
what is the importance of this hardware ID in software Distribution and advertisement in SCCM
shinu

As the name implies, the hardware ID is a unique ID generated based upon the hardware components of a system. The exact algorithm used to generate the ID is not publicly documented or disclosed. Generally, it will change if some hardware component of the
system is changed -- because the algorithm is not known, it's impossible to say what exactly will cause the ID to change so you just have to assume that any hardware change will cause it. You can see the ID is a lot of places including the properties of devices
in the console. The ID itself is meaningless for Software Distributions and Advertisements; however, if a device's hardware ID changes, then it will also be considered a new device and have a new resource generated for it within ConfigMgr. Depending upon how
you are targeting your systems with adverts, this could change what is targeted at that system.
Jason | http://blog.configmgrftw.com

Similar Messages

Duplicate client entries ion Mac OS X 10.5.7 DHCP

I have DHCP server running on Mac OS X 10.5.7 which has duplicate entries for the same client within DHCP. The duplicate client entry has the same ethernet address, same IP but the lease time is different.
I have stopped the service, cleared the DHCP lease and restarted the server and service which seems to clear this for a while but it eventually returns.
Some clients fails to obtain an address from DHCP until you turn off and on the IP setting within the built-in ethernet. When they do two entries appear in DHCP.
I have checked other 10.5 servers that I have installed and the do not experience the same issue this one has.
The lease time for the IP is 2 weeks. Server is connected to Gig network port.
Any help is appreciated..

Found out that the onsite computer support person had enable the second NIC and it had the same IP as the server. Disbaling the second NIC corrected the issue.

SCCM 2007: update fails, client cannot download

Hi,
I have a specific update on SCCM 2007 for Windows 7 clients which clients don't seem to be able to download. It starts the install but fails directly (cannot download).Should I remove this update and redownload? Just right click and "download software
update" or really delete it? If deletion is necessary, how can I retrieve this upate then?
How then?
J.
Jan Hoedt

1 patch took to long to install and that made installation think it failed. It was a non critical patch that solved the issue (we don't install non-critical patches normally that's why we did not notice)
Jan Hoedt

SCCM 2007 SP2 R3 client on App V Server with Terminal Server

Hii,
We have the following servers in our environment.
Termincal Services with Server 2008 and App v on same machine
SCCM 2007 SP2 R3. When I installed SCCM client on APP V server yesterday, terminal and App V servers / services stopped working and users were unable to use these services. After uninstalling of SCCM client, its working. What is the recommendation for this
situation? Is it recommended to do not install SCCM client on APP V servers? And if we install SCCM client then APP V services stop working?
Please suggest.
Regards, Syed Fahad Ali

issue has been resolved via below link.
http://support.microsoft.com/kb/2694295/en-us
the client advertise setting was set to Allow virtual application package advertisement. For the
time being we uninstall the SCCM client from all APP V servers. Soon we will test with the mentioned setting in above link.
Thanks for your response.
Regards, Syed Fahad Ali

Fixing duplicate database entries for the same audio file

My iTunes Media folder is stored on a network accessible storage server. Since upgrading to 11.1.x, my computer seems to be duplicating database entries for the same audio files - for some albums, I have 4 entries for every song, each one pointing to the exact same file. The only difference between entries is rating info and play counts, which are specific to a particular entry (I think). Has anyone else seen this behavior? Is there an obvious way to stop this from happening? I can delete and rebuild the database from media files, but that starts getting old if I have to do it every week or so. Is there a script to delete duplicate database entries? (I found a VB script on the iTunes for Windows community, but the offending machine is a Mac).
Thank you for any assistance!
K

Select the photo stack under the People tab and click the rename icon (bottom left)

Adobe Reader 11.0.04 SCUP update causing SCCM 2007 SP2 R3 client to crash

When we started deploying the 11.0.0.4 update for Adobe Reader provided for System Center Updates Publisher (SCUP), we started having failures with our Operating System Deployments. When the 11.0.0.4 update installs during the Install Software Updates (via WSUS) step, it stops the SCCM client, causing the SCCM client to crash and uninstall. When the SCCM client uninstalls, it breaks the OSD process and the image process fails. Our current .wim file has Adobe Reader 11.x patched to the 11.0.0.3 level. We are using SCUP 2011. Everything was working ok until this update came out. We even tried creating an SCCM software distribution package to deploy the update and it still crashes the SCCM client when installed that way. Has anyone seen similar issues in their SCCM environments? Does Adobe have a support number available to get help with these types of issues? Thanks.

Try using the Adobe doc: 1 Introduction — Enterprise Administration Guide
Also, you'll find installing and updating via bootstrapper is easier than AIP over the long haul.
hth,
Ben

HT1430 I am getting duplicate contact entries of the same person, sometimes up to 10 duplicates. How do I control this?

How can I prevent myiPad contact app from collecting duplicate entries?

once you finalize the addressing the list disappears, so how can is affect the subject . For that matter is disappears when it looses focus.
I have heard of a bug that selects the name that is highlighted when the mouse leaves the selection box if no address is selected. Perhaps that is your issue. Until the issue is fixed I suggest you use tab to leave the address box

SCCM 2012 Secondary site client's are not doing hardware scan for more than 30 days

Hi,
On our SCCM environment around 2500 active clients mapped for particular secondary site not performed hardware scan for more than 30 days. Can anyone provide suggestion how to fix this.
Regards,
Madhan

Yes i confirmed it is listing correct MP and software scan is working fine. we have around 8500 machines connected to that site buy only 3000 machines are having this issue. anyone has faced this issue ?
Only 5000 Computers are supported by a secondary site.
http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigClientNumbers
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Duplicate Library Entries Point to Same File

Hello,
Anyone out there have multiple entries in their main library that point to the exact same physical file? I have a few instances of this and it is little more than any annoyance. It does not appear to sync the same file multiple times to my ipod.
The one difference between the two references is that the directory separator on one of the locations uses all "\"'s whereas the other file has one "/" at the last parent directory.
It is quirky as is iTunes in general. Any feedback is appreciated.
-d

I had something similar, but not exactly. Some of the files showed up twice -- one path was the "long" path (say F:\mp3\Metallica\song file.mp3), and one was the "short" path (F:\mp3\METALL~1\SONGFI~1.mp3). But this only happened because I added my Music folder (F:\mp3) to iTunes again, even though most of the songs were already there. Obviously in most cases it worked fine.
Fortunately for me there were only a few like this, so I just removed them manually.

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

8330 and duplicate calendar entries

For some reason I am getting duplicate calendar entries (of the same event) from multiple email addresses. How to I stop this? I'm using Google sync (working fine) but I get entries from my Hotmail, another local ISP and Juno. And Juno doesn't offer a calendar that I know of. 8330 Curve on US Cellular. Some times just 2 dups sometimes 3. I've cleared the Facebook calendar app on the 8330 (that is my Juno account) But I don't use the Hotmail calendar and the local ISP email doesn't offer a calendar function.

Hi Ridgeroader,
Welcome to BlackBerry Support Community Forums.
It sounds like the calendar invitations are being received in different device calendars. Each email account integrated on your BlackBerry has a calendar associated with it. If your receive an invitation in one email account and accept it, it will be stored in the associated calendar on your device. This KB article and this blog post should provide more information on dealing with multiple device calendars: http://bbry.lv/cBptUW and http://bbry.lv/bozTNY
-FS
Come follow your BlackBerry Technical Team on Twitter! @BlackBerryHelp
Be sure to click Kudos! for those who have helped you.
Click Solution? for posts that have solved your issue(s)!

After upgrading my iphone to v5 software I have duplicate calendar entries - please help

After upgrading my iphone to v5 software I have duplicate calendar entries - please help

Have same issue, reset doesn't help (
I can delete unwanted photos and albums following way:
1) Backup all photos from device (Important!!)
2) Connect to iTunes, enter managing device, select 'Photos' link
3) Select checkbox Sync Photos from <My Pictures>, choose 'Selected folders' but select NONE of them
4) Click Apply, agree to Delete All Photos from device
5) Uncheck 'Sync Photos from', click Apply
Now i have cleared all previous synced folders, that i unable to delete from device.

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 client registration not working.

Hi guys,
i'm in the following situation. Existing SCCM 2007 server at a customers environment. Site is running in Mixed mode. Windows XP clients connected by VPN to the customers infrastructure. The only allowed communication is Port 3333 (http) and Port
3334 (https) from Windows XP to the SCCM Server for Client -> Server Communication. The client is not in the domain, has no DNS and no WINS available. Customer would like to install the SCCM Agent to these computers for hardware inventory purposes.
What I did:
Changed the SCCM Client Communication Port from 80 to 3333 (HTTP)
Changed Site Mode Settings to "Automatically approve all computers" (I know it is not recommended but for first testing, this is ok for us.
Added a host file entry on the Windows XP client to point sccm01.mydomain.local to the appropriate IP Adress of the SCCM Server.
Manually installed the SCCM client on the Windows XP client by using the following command
-> ccmsetup.exe CCMHTTPPORT=3333 CCMHTTPSPORT=3334 SMSMP=sccm01.mydomain.local SMSSLP=sccm01.mydomain.local SMSSITECODE=TST
I see that the client gets installed and shows the correct Site Code etc. but it never appears on the SCCM Server. The ClientIDManagerStartup.log shows that the registration fails:
RegTask - Executing registration task synchronously. 1/1/1601 12:00:00 AM 0 (0x0000)
Evaluated SMBIOS (encoded): 1/1/1601 12:00:00 AM 0 (0x0000)
SMBIOS unchanged 1/1/1601 12:00:00 AM 0 (0x0000)
SID unchanged 1/1/1601 12:00:00 AM 0 (0x0000)
HWID unchanged 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Initial backoff interval: 1 minutes 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Reset backoff interval: 257 minutes 1/1/1601 12:00:00 AM 0 (0x0000)
RegEndPoint: Event notification: CCM_RemoteClient_Reassigned 1/1/1601 12:00:00 AM 0 (0x0000)
RegEndPoint: Received notification for site assignment change from '<none>' to 'TST'. 1/1/1601 12:00:00 AM 0 (0x0000)
GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSE 1/1/1601 12:00:00 AM 0 (0x0000)
Computed HardwareID=2:C0D8D94C7EAA20E943DEDC77694E744B8C147C09
Win32_SystemEnclosure.SerialNumber=
Win32_SystemEnclosure.SMBIOSAssetTag=
Win32_BaseBoard.SerialNumber=
Win32_BIOS.SerialNumber=
Win32_NetworkAdapterConfiguration.MACAddress=xx:xx:xx:xx:xx:xx 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Client is not registered. Sending registration request... 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Failed to send registration request message. Error: 0x80040231 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Failed to send registration request. Error: 0x80040231 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Client is not registered. Sending registration request... 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Failed to send registration request message. Error: 0x80040309 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Failed to send registration request. Error: 0x80040309 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Client is not registered. Sending registration request... 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Failed to send registration request message. Error: 0x80040309 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Failed to send registration request. Error: 0x80040309 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Client is not registered. Sending registration request... 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Failed to send registration request message. Error: 0x80040309 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Failed to send registration request. Error: 0x80040309 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Client is not registered. Sending registration request... 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Client registration is pending. 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Client is pending registration. Sending confirmation request... 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Client is pending registration. Sending confirmation request... 1/1/1601 12:00:00 AM 0 (0x0000)
In the CertificateMaintenance.log on the client I can see the following:
Failed to verify signature for assigned MP. 1/1/1601 12:00:00 AM 0 (0x0000)
Failed to verify signature for assigned MP. 1/1/1601 12:00:00 AM 0 (0x0000)
Failed to verify signature for assigned MP. 1/1/1601 12:00:00 AM 0 (0x0000)
Do you have any idea what I'm doing wrong? Did I miss an important step?
Thanks in advance for any suggestion!
Regards
Stefan

Did you add the SCCM server name and IP in LMHOST File ? if not done please do it and check.
are you able to browse the MP URL ?
https://xxxxxxx.xxxx.com/SMS_MP/.sms_aut?mpcert
but not the other one https://xxxxxxxx.xxxx.com/SMS_MP/.sms_aut?mplist
http://www.windows-noob.com/forums/index.php?/topic/2029-managing-workgroup-computers-in-sccm-sms-environment/
http://www.windows-noob.com/forums/index.php?/topic/8977-how-can-i-remotely-control-workgroup-computers-in-system-center-2012-configuration-manager/
Kamala kannan.c| Please remember to click “Mark as Answer” or Vote as Helpful if its helpful for you. |Disclaimer: This posting is provided with no warranties and confers no rights

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 genarating duplicate client entry becuase of Same Hardware ID

Similar Messages

Maybe you are looking for