Tobie

Hello, Shure, that is not a problem. Just select your C partition when you are about to select which hardrive you wany to install your operating system on. /Tobie

Just an FYI that the Configuration Manager Team blog posted an announcement concerning the Configuration Manager 2007 Service Pack 2 beta that’s scheduled for May 2009. Included are some of the new features so if you haven’t seen it you’ll want to check it out here.

i't seems that you ConfigMgr site have some difficulties to connect to the computers WMI Repository. Error messages like 0x80070005 is always (9/10 times) Access Denied. Or, the WMI Repository is damaged. Check that you have DCOM rights on that machine. Fallow the instructions below. Try running dcomcnfg and right click on My Computer and then select Properties. Check the Default Properties and COM Security tabs and see if anything looks 'not right'. The best way to verify what the setting should be would be to run on a computer where this works and compare the results to one that does not. Unfortunately, I think that this utility must be run locally on each computer. Our you can repair or re-registering your WMI repository on that machine. Go to your Vísta machine and fallow the steps below. Click Start, Run and type CMD.EXE Note: In Windows Vista, you need to open an elevated Command Prompt window. To do so, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. Type this command and press Enter: net stop winmgmt Using Windows Explorer, rename the folder %windir%\System32\Wbem\Repository. (For example, %windir%\System32\Wbem\Repository_bad). %windir% represents the path to the Windows directory, which is typically C:\Windows. Switch to Command Prompt window, and type the following and press ENTER after each line: net start winmgmt EXIT Wait a couple of minutes and try to push out the client again. If you still have problem, try to install the ConfigMgr client manually to see if you get any diffrence. Good Luck /Tobias

DC -> Windows Server 2008 = No problem Uninstall adminpak2003 and install the Active Directory console instead. Post a note if don't now how to do install AD Console when you have been able to uninstall adminpak2003

You should not add a computer account, you should create a new one. I'm possible to choose that option when I creating new computer objects.

It's easy to install a Reporting Point and almost impossible to fail if you fallow anywebs instructions Good luck!

Have you fallowed this instruction when you create a New Server role (Reporting Point)? http://www.windows-noob.com/forums/index.php?showtopic=489

Have you fallowed this instruction when you create a New Server role (Reporting Point)? http://www.windows-noob.com/forums/index.php?showtopic=489

http://<YOUR_SERVER>/SMSReporting_<YOUR_SITE_CODE>/ http://DSGCM1/SMSReporting_DSG/

Have you changed any path recently or when u upgrade your site to a ConfigMgr Site?

Do you mean the "Values" button in the report? Are you missing it?

which "container" is a problem to configure? And where? Please be more specific.

Thanx! Let's hope so

Missing DCOM Rights If you get errors like this then you are missing DCOM rights on the reporting server. Fallow the instruction below to verify if you have DCOM rights and resolve the issue if you are missing it. On your Primary Site, press Start, Administative Tools, Component Services. Expand Console Root, Component Services, Computers, My Computer and select DCOM Config. In the right pane, right click on SMS_REPORTING_POINT and choose Properties. Open the Security tab and press Edit on Launch and Activation Permissions. If the Edit button is greyed out, mark Customize end the press Edit. Verify that YOUR_SERVER\SMS Reporting Users has pemissions as the picture below. Refresh your browser and you should be able to see all reports. /Tobie

Setup access to ConfigMgr Reports It can easily be confusion when it comes ConfigMgr Reports and rights (read) and we will sort things out in this thread and remove all doubts, hopefully. The biggest problem is that administrators do not detect theese problems by themselfs because they are usually members in the local Administrators group on the site server which result in that they have full access to almost everything. Here is an instrcution on "How to grant read access to ConfigMgr Reports by adding the user to a Active Directory Security Group". Create a Active Directory Security Group called ConfigMgrReportViewers. Add a user to this group that need read access to ConfigMgr Reports. On your Primary Site, open Computer Management, expand System Tools, Local Users and Groups, Groups. Double click on SMS Reporting Users to open it, press Add, enter our newly created AD group and hit Check Names, press OK. Verify that your group was added and then press OK. Open http://<YOUR_SERVER>/SMSReporting_<YOUR_SITE_CODE>/ to view ConfigMgr Reports and the result will be like this, no reports, just a menu. (http://dsgcm1/SMSReporting_DSG/). That's not what we want, let's continue... Open your ConfigMgr Console and expand Site Databse and Security Rights, right click on Users and press Manage ConfigMgr Users. Press Next on the Welcome screen. Enter our Active Directory Security Group (ConfigMgrReportViewers) that we created erlier, press Next. Select Add another right or modify existing one and press Next. Select Class: Report Instance: (All Instances) Check Read and press Next. Verify that you selected right Object Class and press Next. Review summary and press Next. Press Close. Now everything is in order to view our ConfigMgr Reports with that specific acount we added to Active Directory Security Group ConfigMgrReportViewers erlier. Open http://<YOUR_SERVER>/SMSReporting_<YOUR_SITE_CODE>/ to view ConfigMgr Reports and the result will be like this, MANY REPORTS (http://dsgcm1/SMSReporting_DSG/). /Tobie

Wasnt u able to repair the WMI Repository in this program?

Try this - The WMI Diagnosis Utility -- Version 2.0 http://www.microsoft.com/downloads/details...;displaylang=en A new utility to help system administrators diagnose and repair problems with the WMI service. Supported Operating Systems: Windows 2000; Windows 98; Windows NT; Windows Server 2003; Windows XP

I can se error 1602 in the logfile which stands for User cancel installation. http://support.microsoft.com/kb/229683 Are u able to install the SCCM Client manually on the computer? Do you get any errors on the screen? You can do that from \\<YOUR_SERVER>\SMS_<YOUR_SITE>\Client. Is there an old SMS Client installed already? /Tobie

I can explain why... You have to tune up Hardware Invetory in your SMS Site. In u'r console, Expand Site Databse, Site Management, %YOUR SITE%, Site Settings, Client Agents. In the right pane, double click on Hardware Invetory Client Agent. Set u'r values and hit OK. /Tobie

How to Backup and Restore DHCP in Windows Server 2008 In Windows Server 2008, backup of DHCP database and settings has gotten simpler. You may want to backup your DHCP server from time to time to prepare for disaster recovery scenarios or when migrating DHCP server role to a new hardware. Backup DHCP Server 1. Open Server Manager > DHCP role 2. Right click server name, choose Backup.. 3. Choose a location for backup, click OK Restore DHCP Server 1. Open Server Manager > DHCP role 2. Right Click server name, choose Restore 3. Choose the location of the backup, click OK 4. Restart the DHCP Service

Enable Remote Desktop (RDP) on all computers/servers with Group Policy Object (GPO) Open Group Policy Management console and expand the policy that you want to edit, right click and choose Edit. I will edit my Defualt Domain Policy since I want to be 100% shure that RDP is enabled on all my clients and servers. When the Group Policy Management Editor appears, expand Computer Configuration, Policies, Administrative Templates, Windows Component, Terminal Services, Terminal Server, Connections, double click on the policy called Allow users to connect remotely using Terminal Services. Set it to Enabled. All done, refresh the policy on your clients/servers with command: GPUPDATE /FORCE. /Tobie

I think that we are on wrong track since it was not working when u removed the existing GFX drivers, why should it work with a newer driver? You mentioned that you can distribute SCCM Client to other computer without 2 monitors. I would like to take a look at u'r logfiles pls.

The best thing to do is to create u'r own MSI-package with all information/switches needed to carry out u'r desired work.

This is one of my favorites of ur's!

Confige Distribution Point settings for this package Expand Computer Management, Software Distribution, Advertisements, right click on your advertisement and choose Properties. Click to clear Allow clients to fallback to unprotected distribution points when the content is not available on the protected distribution point, and then click OK.