Configuration Manager Remote Control Disabled after install

After installing the Configuration Manager client on a Windows XP workstation. The client appears to install fine but the Configuration Manager Remote control service is stopped and the startup type is set to disabled. My ccmsetup.log says the install was successful and the client shows up in the configuration manager console.
 
To solve this issue, start by changing the following values in the registry:
 
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\Client Components\Remote Control
 
Access Level 0 => 2
Allow Local Administrators to do Remote Control 0 => 1
Audible Signal 1 => 0
Enabled 0 => 1
Firewall Exception Profiles 0 => 15
Permission Required 1 => 0
PermittedViewers Administrators => blank
 
Finally, set the service Configuration Manager Remote Control to Automatic and start it.
 
Source: http://www.myitforum.com/forums/Configuration-Manager-Remote-Control-Disabled-after-install-m238614.aspx
 
I do not know why this happened, but I'm suspecting that it has something to do with the client not being assigned to a boundary group.
 
 

Failed to get client identity (80004005)

PXE keeps rebooting after Preparing network connections.
 
Errors in smsts.log:
 
reply has no message header marker
Failed to get client identity (80004005)
failed to request for client
 
Resolution: Set correct time and date in BIOS
 
Source: http://msitpros.com/?p=58
 
 
 
 

Restricting booking of conference rooms

If you run the following command you will see that the default BookInPolicy is set to true, which means that everyone can use this resource.
 
Get-CalendarProcessing -Identity room-alias | fl *policy*
 
If you want to restrict access to this resource, set this to false.
 
Set-CalendarProcessing -Identity room-alias -AllBookInPolicy:$false
 
Then run the same command but exchange :$false with the mailbox user or the distribution group which should have access to the resource.
 
Set-CalendarProcessing -Identity room-alias -AllBookInPolicy <mailbox user/distribution group>
 
If you want to revert the changes made, run the following commands.
 
Set-CalendarProcessing -Identity room-alias -AllBookInPolicy:$true
Set CalendarProcessing -Identity room-alias -BookInPolicy:$none
 
 

SCCM Agent not working after OS deploy

The agent doesn't get the self signed certificate after os deployment.
 
Right after the "Setup Windows and ConfigMgr" step, add two "Run Command Lines" to set the registry values correctly. Here are the two commands to be run:
 

REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec /v ProvisioningMode /t REG_SZ /d false /f

 

REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec /v SystemTaskExcludes /t REG_SZ /d "" /f

 

Please read more here: http://www.windows-noob.com/forums/index.php?/topic/5618-damaged-client-after-setup-no-self-singed-cert/

 

 


Time Configuration in a Windows domain

To configure the Domain Controller with the PDC Emulator FSMO to another time source, run:

w32tm /config /manualpeerlist:PEERS /syncfromflags:manual /reliable:yes /update

Please set for PEERS the time source as listed above, either with it’s ip address or DNS name. If more then one is needed separate them with a space in between and don't forget the quotes: "time.domain.com time1.domain.com"

Internet Time servers you can find here: http://www.pool.ntp.org/

 

Tto configure a domain computer for automatic domain time synchronization, run:

w32tm /config /syncfromflags:domhier /update
net stop w32time
net start w32time

 

To reconfigure the previous PDC Emulator, in case of transferring/seizing the FSMO to another Domain Controller, run:

w32tm /config /syncfromflags:domhier /reliable:no /update
net stop w32time
net start w32time

 

If you have to reconfigure a Windows 2000 Server Domain Controller, the steps are different after transferring/seizing the PDC Emulator role to another Domain Controller:

- you have to modify the "Type" value to "Nt5Ds" without the quotes under this registry key:

HKLM\ SYSTEM\ CurrentControlSet\ Services\ W32Time\ Parameters\

 

If you have problems with the time service configuration, because too many changes where done in the registry or you like start fresh on a computer, then you can reset the time service to a default state the following way. Make sure to use an elevated command prompt, to have full administrative permissions. Then type in the following commands:

net stop w32time

w32tm /unregister

w32tm /register

net start w32time

 

To check Domain Controller synchronization, run:

w32tm /monitor

 

To check a domain computers configuration, run:

w32tm /query /status


RSS 2.0