SCCM 2007 R2 - configuration item compliance for a collection.

Hi All,
Can some one share the information of reports for configuration item compliance of for a collection in SCCM 2007 R2 using desired configuration management feature.
Rgs,

Yes, but no data shows up.
What does this mean? What troubleshooting have you done? When do you create the DCM?
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Similar Messages

Split configured item lines for shipping

We use Configurator (CZ) and we're having trouble splitting a line for shipment. If we have 100 of the same configured item on line 1.1 in the sales order we are unable to ship just 10 of them and backorder or do anything else with the other 90. The system wants us to ship all 100 at once. We don't have this problem with non-configured items.
Any ideas? Metalink has been pretty worthless (as usual) in giving me any info.
Thanks!

Has data for any other items got collected in M1? If not, then the problem could be your collection group or og-instance setup. Have you used the organization access screen in ASCP admin responsibility and granted access to M1 for your responsibiilty?
Is the item marked as planned in M1?
Sandeep Gandhi

SCCM 2007 standalone USB is prompting for media

Hello. I have been creating standalone media on USB for a while. This week I needed to create new standalone media with an updated image and 3 new packages.
I modified the same TSs in SCCM 2007 I always use to create the standalone media on USB. The USB sticks are 16 gig and I diskpart like usual.
After creating the new standalone media on USB, I tested the sticks.
It deploys the image and drivers successfully but when it is attempting to install the packages (applications) I get a popup asking me to insert the media for the install.
I checked the USB stick and the packages are all there and I can launch the packages successfully.
I also advertised the TSs and can deploy via advertisement.
Any ideas? I have to get these done as soon as possible. WIll appreciate the help.
Charles

Did you find the source of the problem? I am running into the same issue but it appears to only occur on certain brands or models of USB stick.
Also, unplugging the stick, plugging it back in, and clicking OK on the media prompt allows the process to continue.
BWitz

Can I use SCCM 2007 to deploy SCCM 2012 Agent

I was reading the scenarios for deploying the SCCM 2012 agent here
http://technet.microsoft.com/en-us/library/gg682132.aspx
I have been planning to deploy the 2012 agent using an SCCM 2007 deployment package. I am not migrating any data/packages/collections/anything from SCCM 2007.
I am looking for a sane way to deploy 2000ish clients a day for 2 weeks and be done.
I figure they are all SCCM 2007 clients so lets deploy 2012 agent using SCCM 2007.
I read the following in the link above and it sounds like the way I want to go – use SCCM 2007 software distribution…
Upgrade installation by using application management
Upgrades clients to a newer version by using Configuration Manager application management. You can also use Configuration Manager 2007 software
distribution to upgrade clients to System Center 2012 Configuration Manager.
Then later in the same document there is this…
How to Upgrade Configuration Manager Clients by Using a Package and Program
You can use Configuration Manager to create and deploy a package and program that upgrades the client software for selected computers in your hierarchy. A package definition file
is supplied with Configuration Manager that populates the package properties with typically used values. You can customize the behavior of the client installation by specifying additional command line properties.
You cannot upgrade Configuration Manager 2007 clients to System Center 2012 Configuration Manager by using this method.
In this scenario, use automatic client upgrade, which automatically creates and deploys a package that contains the latest version of the client.
What???!?? There is no Automatic client upgrade feature in 2007 – so how does that even make sense? In one section, it says I can deploy the 2012 Agent using SCCM 2007 software distribution, and then later in the same document, it
says I can't. I am probably misunderstanding somthing.
Is it possible to make a package/program in SCCM 2007 that will make targeted clients upgrade to Agent 2012 and join the new SCCM 2012 Site?

I tested this (deploying 2012 agent using existing 2007 SCCM infrastructure) with a few test systems at my desk and it seems to work pretty smoothly. I made a package to deploy SCCM 2012 SP1 and added it to my SCCM 2007 Site. Then I deployed
the 2012 agent from 2007 and it worked great. If it works this well in production, I will be able to migrate all of my clients in less than a weeks time.
I have not published the 2012 site information in AD - and I don't plan to. We would have some overlapping site boundaries - and in 2012 it seems its unnecessary in a single site hierarchy. I AM planning to use boundaries to assign
DPs, but thankfully site and DP boundaries have been separated. It works great to just specify the site in everything and not worry about auto discovery. My clients don't move among sites since I only have one large site.
Sorry that I somehow posted this same question twice, and thanks for cleaning that up.
In my installation, I just called ccmsetup.exe with the following command line...
/mp:myMP.mydomain.com CCMLOGMAXHISTORY=5 CCMLOGMAXSIZE=1000000 SMSCACHEFLAGS=PERCENTDISKSPACE;NTFSONLY SMSCACHESIZE=10 SMSMP=myMP.mydomain.com SMSSITECODE=CCM
I am not sure that I need to specify the MP twice, but it is working to do so. I'm also not sure whether the log and cache flags will be honored since there are existing settings from SCCM2007 agent. I think that the 2012 install will not change
these settings upon installation, but it does not appear to hurt the process to include them just in case it does work.

Can you deploy an application sequenced with App-V v5 with SCCM 2007?

We are currently in the process of upgrading to SCCM 2012. We are also embarking on testing App-V v5. Can we deploy sequenced applications from App-V v5 using SCCM 2007? What limitations will exist with SCCM 2007? What release of
SCCM 2007 should we be at for App-V v5 sequenced applications to be deployed and/or streamed?

This KB article is now available: Supported Configuration Manager and Microsoft Application Virtualization scenarios
Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or click "Unmark as Answer" if a marked post does not actually
answer your question). This can be beneficial to other community members reading the thread.
This forum post is my own opinion and does not necessarily reflect the opinion or view of my employer, Microsoft, its employees, or other MVPs.
Twitter:
@stealthpuppy | Blog:
stealthpuppy.com |
The Definitive Guide to Delivering Microsoft Office with App-V

MOF file migration from SCCM 2007 to SCCM 2012

Hi,
I have an issue while migrating SCCM 2007 MOF (Configuration.mof) to SCCM 2012,Problem is...
In our infrastructure, We have integrated our custom inventory classes with the logon script.Now we are migrating to SCCM 2012.When i migrate the same Custom inventory classes to SCCM 2012,I can able to compile/migrate, However SCCM 2012 views are not in
sync with SCCM 2007.
Example: If i use SCCM 2007 collection/Query in SCCM 2012 that uses these custom inventory classes, its thrown an error saying that objects in this query are not valid, because of this none of the collections/Queries that uses old inventory classes are not
working.
I dont want to change anything in the logon script...
Can someone please help me on this.Thanks in advance..
srkr

Hi Garth,
Thanks for the reply.
As per my understand,there's nothing to do with SMS_DEF.mof and only Configuration.mof can be editable.
When you say Importing sms_def.mof in SCCM 2012,I guess there's is something i missed out.
Below is the both SMS_DEF.mof and Configuration.mof from SCCM 2007, Also please let me know how to import SMS_DEF.mof in SCCM 2012
************SMS_DEF.MOF*********************
//-- SCCM Report: XXX_AD_Info
[SMS_Report(TRUE),
SMS_Group_Name("XXX AD Info"),
ResID(6200),
ResDLL("SMS_RXPL.dll"),
SMS_Class_ID("XXX|EDADInfo|5.0")]
class XXX_AD_Info
[SMS_Report(TRUE), key]
string KeyName;
[SMS_Report(TRUE)]
string Distinguished_Name;
[SMS_Report(TRUE)]
string AD_Site;
[SMS_Report(TRUE)]
string DCName;
[SMS_Report(TRUE)]
string MachineDomain;
*********Configuration.mof*******************
//--SCCM Instance: XXX_AD_Info
[DYNPROPS]
class XXX_AD_Info
[key]
string KeyName;
string Distinguished_Name;
string AD_Site;
string DCName;
string MachineDomain;
//--SCCM Instance: XXX_AD_Info
[DYNPROPS]
instance of XXX_AD_Info
KeyName = "XXX AD Info";
[PropertyContext("local|HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy\\State\\Machine|Distinguished-Name"), Dynamic, Provider("RegPropProv")]
Distinguished_Name;
[PropertyContext("local|HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy\\State\\Machine|Site-Name"), Dynamic, Provider("RegPropProv")]
AD_Site;
[PropertyContext("local|HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy\\History|DCName"), Dynamic, Provider("RegPropProv")]
DCName;
[PropertyContext("local|HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Group Policy\\History|MachineDomain"), Dynamic, Provider("RegPropProv")]
MachineDomain;
srkr

Lenovo X1 Carbon PXe boot errors with SCCM 2007

I know there are many posts on this and I've gone through them all, but I am still having issues PXe booting a X1. I have a USB ethernet dongle (the new type with the rounded edge). the part number is 0b67708. It's branded Lenovo but when I pxe it recognises it as ASIX AX88772b. So far so good. It picks up an IP from DHCP ok, recognises the hardware as x64 and then tries to download the \smsboot\boot.sdi file from the SCCM 2007 server. It waits for 20 seconds then falls over with the following:
Status: 0xc0000001 - Info: The boot selection failed because a required device is inaccessible.
Now, I have the the following drivers in the boot.wim file:
x86 -
1. Lenovo USB2.0 Ethernet Adapter 5.12.7.0
2. PCI bus
3. Intel ICHR/DO/DH SATA AHCI Controller
4. Intel USB 3.0 Root Hub
5. Intel USB 3.0 eXtensible Host Controller
x64 -
1. Lenovo USB 2.0 Ethernet Adapter 5.14.4.0
2. PCI Bus
3. Intel ICHR/DO/DH SATA AHCI Controller - 2821
4. Intel USB 3.0 Root Hub
5. Intel USB 3.0 eXtensible Host Controller
I have tried using the ASIX drivers, all previous driver version, adding in the mass storage drivers, adding in the USB 3.0 drivers, praying to the PXe gods but nothing works.
All other hardware works fine. Any suggestions greatly welcomed.
Cheers - Mark.

Make a USB recovery drive before reinstalling.Thats the only option with a preload. With a retail serial number, you can download an iso with the upgrade assistant.
Also, how much ram do you have. If yopu have more than 4GB, you will need 64 bit XP, or the performance will take a hit. I tried XP on my W530, but I had to change several settings in the BIOS/UEFI.
W530(2436-CTO): i7-3720QM, nVidia Quadro K2000M,16GB RAM, 500 GB hard drive, 128GB mSATA SSD, Ubuntu 14.04 Gnome, Centrino Ultimate-N 6300.
Yoga 3 Pro: Intel Core-M 5Y70, Intel HD 5300, 8GB RAM, 128GB eMMC, Windows 8.1, Broadcom Wireless 802.11ac.

Monitoring for a collected file

Hi there folks
I have a need to use SCORCH to perform some automation based upon a file. Essentially this is what I wish to do
- Write a text file to a share on an SCCM client. There will in fact be a number of SCCM clients
- The folder is monitored for file collection
- The file will be transferred to SCCM Site Server
- I want SCORCH to be able to look into SCCM for a number of known SCCM clients to identify that a new file has been collected, read the filename and then start processing the file. Ideally I'd then like to have SCORCH delete that file.
It's that last stage which is causing me some concern as I cannot see how to programmatically get into File Collection and extract the text file. Is there a script which we can access on this at all?

Hi Torsten
OK, it's a bit complicated but I have a branch office like scenario but each is an untrusted forest. I have a server down on the branch which is an MP, SUP, DP and SCCM client and it manages a bunch of SCCM clients down in the branch. This server
also functions as a SCOM gateway for managing the infrastructure boxes.
Down in the branches however I have a bunch of boxes which cannot have an SCCM client installed on them (even with the new clients) which from a central location need to have jobs run on them.
At head office I have a package for each Branch and I write a job file for a system in the form SYSID-TicketID.JOB where SYSID is the name of the system and ticket ID is what Remedy built. The .JOB file goes into the package and the package content
is refreshed. The .JOB file finds it way down through SCCM and eventually arrives at the branch and is copied to the share. At the branch, systems will look in the share and see that there is .JOB file for them. They will do something at
this stage.
When the system is performing its stuff it will write to a share on the SCCM client called BACKCHANNEL a file called SYSID-TicketID.LOG. Through file collection SCCM delivers this file back to the SCCM server.
Now, we need SCORCH to be able to look into SCCM for any collected files and then extract them, adding the .LOG file to the ticket in Remedy. When this is done we want SCORCH to be able to remove the .LOG file from SCCM and then to remove the .JOB
file from the package source. The next time a new .JOB file is created there and the content refreshed the old .JOB will be removed from the DP and the new .JOB sent down.
Yes, it is complicated in a way

Configure WSUS for SCCM 2007 to received patchs and deploy

Dears,
I have installled SCCM 2007 and WSUS server in another server now i want to confiure for patching.
how to do that and and ensure SCCM 2007 server receiving patchs.
Please assist.
[email protected]

Hi,
Would suggest you read the below on how to create/configure a SUP
http://technet.microsoft.com/en-us/library/bb633236.aspx
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

Using Echo Command in PowerShell Script for Configuration Item

Hello All,
Before you tell me to post my PowerShell question to the PowerShell Forum, please know that the PowerShell portion of my task works just fine. It is the SCCM portion of my task that keeps failing, so that is why I am here. To give some background...
There are two servers in our SCCM test environment. Both the SCCM server and SQL DB server are 2012, patched and updated.
Test servers in my Device Collection being used for running Baselines and Reports against are 2008R2 and 2012, patched and updated.
I have created a Configuration Item that checks to see if the FTP Server Role Feature has been installed on a 2008 or 2012 server. To do the check, I am using the following PowerShell script:
(get-windowsfeature -Name Web-Ftp-Server).Installed
When I log into my 2008R2 and 2012 test servers, and run this command directly on the server, it will return a "True" if the FTP Server Role Feature is installed on either server, and a "False" if it is not installed. Basically,
it works as advertised.
When I setup my Configuration Item and then deploy my Baseline, or run a report against my device collection of test servers, SCCM will return a correct response (True or False) for the 2012 test server, but throws the following error for the 2008R2
server:
0x87df00329 application requirement evaluation or detection failed
Google searches for this have not been very helpful.
Now, when I created the Configuration Item and referenced PowerShell, the configuration screen has the following note:
"Specify the script to find and return the value to be assessed for compliance on client devices. Use the echo command to return the script value to Configuration Manager."
Since I did not include an echo command in my PowerShell script above, I figured that was my problem, so I did the following:
Logging onto both of my test servers (2008R2 & 2012) I was able to successfully run the following PowerShell commands and get the expected responses of True or False:
(get-windowsfeature -Name Web-Ftp-Server).Installed | echo
(get-windowsfeature -Name Web-Ftp-Server).Installed | write-output (http://technet.microsoft.com/en-us/library/hh849921.aspx)
(get-windowsfeature -Name Web-Ftp-Server).Installed | write-host (http://technet.microsoft.com/en-us/library/ee177031.aspx)
However, when I use any of these PowerShell commands in my Configuration Item, NEITHER of my test servers returns a response to the SCCM server.
When I check the report, both servers show as "Unknown" and when I click on the number 2 (as in 2 servers unknown), the following report page (List of unknown assets for a configuration baseline) has absolutely no data/information at all.
So...I am at a loss.
SCCM tells me to use an echo command to return a script value to Configuration Manager. The PowerShell scripts above, with the various echo related commands, work just fine on the servers themselves, but they return no information when run via SCCM.
What am I missing?
Any help will be appreciated.
Thanks in advance for your time.

Sorry for my ignorance, but I don't understand. (I forgot to mention that I am new at both PowerShell and SCCM.)
After I change the PowerShell script to add the echo/write-output/write-host cmdlet, I open the ConFig Item and "Clear" the PowerShell script and then re-add it. When I do that, it correctly shows the change in the ConFig Item.
Next I open the Baseline, then open the ConFig Item within the Baseline to make sure the change is reflected there as well, which it is.
I then deploy the Baseline to my Device Collection. After that, I run a report against the Baseline and Device Collection and it returns the "Unknown" result.
If I open the PowerShell script and remove the echo/write-output/write-host cmdlet, then go through the rest of the process of updating and reporting, the result it returns changes, showing one server in compliance and the other server out of compliance,
which leads me to think that all changes have taken correctly.
Does that sound right? If I manually deploy the Baseline, is that the same as the client retrieving policies from the management point?
Sorry to be so thick but I'm learning as I go.
Thanks again for your help.

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.

"Enable distribution-point sharing for this source site" did not showing SCCM 2007 DPs as SCCM 2012 content shares for CM12 clients

Hi
We have one central site server and three primary site servers in SCCM 2007 and completed the SCCM 2012 migration as single hierarchy.
During the migration, We have configured SCCM 2007 Central site server as source hierarchy for data gathering process and configured the "Enable distribution-point sharing for this source site" to make SCCM 2007 distribution points
as SCCM 2012 content shares to serve SCCM 2012 migrated clients. Now we are facing a problem that one of the primary site server's data gathering process did not gather SCCM 2007 DPs even though we configured "Enable distribution-point sharing for this
source site" but data gathering process is completing successfully.
Is anyone have idea, why these SCCM 2007 DPs did not appearing as SCCM 2012 content shares under "Shared Distribution Points"
Thanks in Advance
srkr

Now we are facing a problem that one of the primary site server's data gathering process did not gather SCCM 2007 DPs even though we configured "Enable distribution-point sharing for this source
site" but data gathering process is completing successfully.
Earlier all the shared DPs are showing under Shared Distribution Points ? Or since starting itself these DPs are not showing down? Have you checked migmctrl.log for some clue?
Anoop C Nair (My Blog www.AnoopCNair.com)
- Twitter @anoopmannur -
FaceBook Forum For SCCM

Server showing non compliant for a no longer targeted Configuration Item

Hi all,
I have a server that was removed from a collection which had a DCM baseline targeted to it. It is still showing non compliant for Configuration items that were targeted at the old collection. (which is correct, it isn't compliant but it isn't supposed
to be). I am trying to create a collection based on non compliant items but this server keeps showing up where it shouldn't be. is there anyway to 'flush' all the compliance information and let the client rebuild it?
thanks
-cornasdf
http://cornasdf.blogspot.com

The collection is based on a WQL query that basically says, where the configuration item name = x and state <> compliant.
I have several of these where the servers that are non compliant fall into a collection that has an advertisement that remediates them.
The difficulty here is that I have a collection of BackEnd servers, based on IP Subnet. That collection has a DCM Baseline targeted at it that checks for non compliance on specific items. When building
some new servers, we connected to hte wrong network for a couple of days, so they were in the included in BackEnd Servers collection which handed out the baseline. We disconnected that link and the servers have fallen out of that collection. The
baseline no longer shows in teh control panel app.
But in my compliance collections, it still shows up as non compliant for that Conf Item.
I have a work around in place. actually two. The first was to just delete the client and let it reinstall. That worked but seems heavy handed. Secondarily, i narrowed my query by collection,
ie the query for non compliance now is limited to the collection where I apply the baseline. this is somewhat limiting for future instances (and shouldn't be necessary).
it seems like a bad enough design flaw that I assumed I must be missing something pretty obvious. if I remove a server from a collection w/ a baseline, it shouldn't still be non compliant for things non longer targeted to it.
-cornasdf
http://cornasdf.blogspot.com

FEP Exemptions for SCCM 2007 Server

I configured a policy for my SCCM 2007 site server and used the SCCM Server Template. It came populated with the %programfiles%\Microsoft Configuration Manager\Inboxes\*.box. I found today that my SCCM server was backing up processing hardware inventory
and I looked at the %programfiles%\Microsoft Configuration Manager\Inboxes\Auth\dataldr.box and found over 6000 there. I added that path to my exclusions in the policy but it did not speed up .mif processing. Only when I turned of real time protection did
the backlog clear up. Is there a process that I might exclude that might be getting blocked? Should I post this in the SCCM forum?Orange County District Attorney

This is old post and there have been several changes in SCCM, and Forefront, specially successor for Forefront is System Center Endpoint Protection which integrated into SCCM. You could define filtering for both process and files and it should work, but
you might wait or enforce policy update on clients.
If possible try reproduce the problem in SCEP and check if it reproduce or not?

Does SCCM 2007 R3 support SQL 2014 if not is there any mitigation plan for this

Hi ,
As part of Database migration to SQL 2014, wanted to check whether SCCM 2007 R3 support SQL 2014 or not.
I have a link for SCCM 2012 which tells it does support to SCCM 2012, but in upgrade mode.
Is there any other approch instead of upgrade on SCCM 2012.
Please let us know.
http://windowsitpro.com/configuration-manager/configmgr-2012-supported-sql-server-2014-only-if-you-upgrade
Regards
Sudam Bisi
CTS

I doubt CM07 will support SQL 2014, particularly when mainstream support has ended already.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCCM 2007 R2 - configuration item compliance for a collection.

Similar Messages

Maybe you are looking for