Kevin79

I just did some testing. All of my OSD task sequences show up when I boot to PXE with an unknown computer. Any idea if this can be changed?

Thanks but I'm still confused. My primary site was installed with Configuration Manager 2007 SP2 Evaluation version and then had R2 Evaluation version installed. I installed my secondary site from my primary site by using "New Secondary Site" and then "Copy installation source files over the network from the parent site server". Would that not then install the evaluation version of Configuration Manager on the secondary server? If so, why is it not letting me install R2 evaluation version on top of it?

I am trying to use the evaluation version. That is what my primary site is installed with as well. I'm trying to see if SCCM will fit the needs of the company.

I installed SP2 (well, repaired it since that was my only option) and it still won't let me install R2.

I just tried to install R2 and it failed. It says "The evaluation version of Microsoft System Center Configuration Manager 2007 R2 can only be installed on an evaluation Configuration Manager Service Pack 1 site or higher." The site was installed from a primary site that is SP2 R2 evaluation. Any suggestions on how to install R2?

I haven't really tried anything yet but I've noticed that there isn't a way to limit an advertisement to a specific site unless I am missing something.

Is there a way to have task sequences show up on certain servers? I.E. I have enabled unknown computer support so that I don't need to pre-assign them in SCCM. I will eventually have 8 different sites and each site will need to have different settings in the task sequence. Some are in different time zones and each site has a specific OU that the computer needs to go in. I would rather not give the remote IT support the option to choose a TS for a different site so I only want them to see the ones from their site.

I'm configuring a server to be a secondary site. The server is running Windows 2003 R2 SP2 32bit. I have it all working and installed the PXE service point. I don't get the option to "Enable unknown computer support" in the properties like I do with my primary site that is running 2008 R2. Do I need to install MDT on my secondary server in order to enable this option?

It looks like Lenovo puts different model numbers for every PC, even if the configuration is the same. I have two identical notebooks with different model names.

I'm confused. How do I have it search for bluetooth on the computers?

That won't work because not all of my T400s have bluetooth. Is there a query that will tell if there is bluetooth on the computer?

I have Lenovo laptops that I want to use with SCCM OSD. Some of the laptops have bluetooth, some don't. Some have fingerprint readers, some don't. Is there a way to only install the bluetooth and fingerprint software on the devices that actually have them? I can't choose a model since it varies (I.E. We have ThinkPad T400s that have bluetooth but not all of them do).

Thanks. It is working now.

I have an OSD TS that mostly works fine. The OS is installed and the ConfigMgr client is also installed. The problem is that none of the drivers are installed. The drivers for my NIC and chipset are added to SCCM and a driver package was created. My TS has the section "Apply Device Drivers" and is set to "Install all compatible drivers" and "Consider drivers from all categories". My NIC or chipset drivers are never installed though. I doesn't look like they are copied over during the OS either. The folder c:\drivers is created and has the file INFCACHE.1. Any idea's how I can find out what is wrong?

I am trying to make the deployment look like it is in MDT so that my remote IT support doesn't get confused.

I'm trying to edit my process of deploying images in SCCM (I know wrong forum but read on!) to make it look more like MDT. In our current MDT environment, MDT automatically fills in the fields for the domain (name of the domain, username, password, OU). Where is this saved? I want to try to pull the same information in in SCCM. Thanks!

Anyweb, Thanks for this tutorial (and pointing me to it in my other thread). At the end, you say There isn't a link to click though and a quick look at the forum doesn't show part 2. Where can I find this?

I am currently using MDT to deploy my images across the corporation. I like how the interface is for the installation of the image, is there a way to make SCCM's like this? My sites have local people that are imaging computers but IT isn't their primary role. It is nice to have them see the images they can choose and then have it ask them for the computer name and give them the option to change the OU (this one is mostly nice for the main IT department if they are putting an image on a computer that belongs to a different site) and/or domain, and change the time zone. Is there a way to make it so that SCCM asks this information as well? Also, my IT support will redo computers when the computer starts slowing down or the user leaves the company. Is there a way to let them put an image on a computer that is already in SCCM without a) having them call me to remove the computer from SCCM or creating an advertisement to all computers that shows up in "Run Advertised Programs"? Thanks in advance!

That directory doesn't exist. Like I said, it doesn't look like it is installed. I followed the guides from here and IIS and all the components are installed.

Anyone?

I tried that and even ended up reinstalling the OS and SCCM. I still can't get the Reporting Point to install. Same error messages.

The status messages are: They all have: Date: 9/18/2010 Site Code: <Site Code> System: <Server Name> Source: SMS Server Component: SMS_REPORTING_POINT Type: Milestone Time: 8:15:41.267 AM Severity: Information Message ID: 1018 Process ID: 2216 Thread ID: 3736 Description: SMS Site Component Manager is reinstalling this component on this site system. Type: Detail Time: 8:45:47.607 AM Severity: Error Message ID: 1083 Process ID: 2216 Thread ID: 3736 Description: SMS Site Component Manager successfully used the SMS_SERVER_BOOTSTRAP_CORP-SCCM service to run the following program on site system "\\CORP-SCCM": C:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\rpsetup.exe /deinstall /siteserver:CORP-SCCM The program failed for the following reason: Child process "C:\PROGRA~2\MIE096~1\bin\i386\rpsetup.exe /deinstall /siteserver:CORP-SCCM" took too long to execute, and the process (PID = 4376) was orphaned. Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. SMS Site Component Manager cannot install component SMS_REPORTING_POINT until the program runs successfully. If this problem persists and you cannot fix it, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. Type: Detail Time: 8:45:47.613 AM Severity: Information Message ID: 1079 Process ID: 2216 Thread ID: 3736 Description: SMS Site Component Manager did not copy file "C:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\system32\msvcp60.dll" to "C:\Windows\system32\msvcp60.dll", because the source file is not a newer version than the destination file. Type: Detail Time: 9:15:53.853 AM Severity: Error Message ID: 1083 Process ID: 2216 Thread ID: 3736 Description: SMS Site Component Manager successfully used the SMS_SERVER_BOOTSTRAP_CORP-SCCM service to run the following program on site system "\\CORP-SCCM": C:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\rpsetup.exe /install /siteserver:CORP-SCCM The program failed for the following reason: Child process "C:\PROGRA~2\MIE096~1\bin\i386\rpsetup.exe /install /siteserver:CORP-SCCM" took too long to execute, and the process (PID = 2116) was orphaned. Possible cause: SMS Site Component Manager does not have sufficient access rights to administer the site system. Solution: Verify that the Site System Connection accounts are properly configured to allow SMS to administer the site system. SMS Site Component Manager cannot install component SMS_REPORTING_POINT until the program runs successfully. If this problem persists and you cannot fix it, refer to your SMS documentation or the Microsoft Knowledge Base for further troubleshooting information. Type: Milestone Time: 9:15:53.863 AM Severity: Error Message ID: 1020 Process ID: 2216 Thread ID: 3736 Description: SMS Site Component Manager failed to reinstall this component on this site system. This repeats every 60 minutes. The reporting role does not seem to be installed correctly. SMSReportingInstall.LOG doesn't show any errors in it but it also hasn't been written to since 9/15/2010. I don't have a smsreporting.log file.

I am rebuilding my test server and followed the installation guides from this site. If I look in the Component Status though, I have a critical status for SMS_REPORTING_POINT. I'm not sure what log to look at on the computer, but I can see errors in the Status Message Viewer. What log file should I post?

How do I determine which site server discovered the computer?

So if I tell it to Install from the SCCM console, it will always install from the primary site?