The ConfigMgr console could not connect to the ConfigMgr site database

The ConfigMgr console could not connect to the ConfigMgr site database. Verify that this computer has network connectivity to the SMS Provider computer and that your user account has Remote Activation permissions on both the ConfigMgr site server and SMS Provider computers. For more information, see "How to Configure DCOM Permissions for Configuration Manager Console Connections" in ConfigMgr Help.


Solution: 


Rebooted Windows 2008 server and the connection worked again. 

How to Enable Remote Control in WinPE 2.0 (SCCM OSD)

Note: It seems this post is starting to become quite popular. I'm going to re-write this and include some pictures to make it easier to setup. 


I recently spent some time figuring out how to enable remote control in WinPE 2.0


What you need:
- WinPE2.0
- TightVNC beta client (2.x)
- Access to your Boot.wim files and ImageX.
- Regedit access in your boot.wim.
- VBscript knowledge.


Basically what we are going to do is write a script that:
- Disables the inbuilt firewall included with WinPE 2.0
- Imports a few registry entries for TightVNC
- Installs TightVNC as a service and then starts it.


Then we'll edit our boot.wim to execute our start up script before the Task Sequence prompt is is show so the service is installed,enabled and waiting for remote control.


1. Source the TightVNC files: You need the latest Beta software as the current standard software will not work in WinPE 2.0 because of vista's new security of  launching all services in a different system account to normal (system0/1)


Extract the Tight VNC files and then you need to grab the TVNserver.exe and Screenhooks.dll.  (also under the GPU you need to copy the license files I believe.)


Copy these files to a temp directory to allow us to set up the application and test it.


2. Next  you need to create a vbs script  like the following;


=========================================
'Installer Script for TightVNC Service for WINPE
'Version: 1.0
'Created: 29/04/2010
'Created By: JoeJoeinc.com


'Disable firewall,Import VNc settings,Install the service,Start the service.


'Define WshShell
Set WshShell = CreateObject("Wscript.Shell")

'Disable WINPE Firewall
WshShell.Run("wpeutil disablefirewall"),0,True
'Import VNCSET.REG
WshShell.Run("regedit /S vncset.reg"),0,True
'Install the VNC service
WshShell.Run("tvnserver.exe -install -silent "),0,True
'Start the VNC service
WshShell.Run("tvnserver.exe -start "),0,True
======================================


Save it as install.vbs


Next create a registry file like the following..


Windows Registry Editor Version 5.00


==============================================
[HKEY_LOCAL_MACHINE\SOFTWARE\TightVNC\Server]
"ExtraPorts"=""
"QueryTimeout"=dword:0000001e
"QueryAcceptOnTimeout"=dword:00000000
"LocalInputPriorityTimeout"=dword:00000003
"LocalInputPriority"=dword:00000000
"BlockRemoteInput"=dword:00000000
"BlockLocalInput"=dword:00000000
"IpAccessControl"=""
"RfbPort"=dword:0000170c
"HttpPort"=dword:000016a8
"DisconnectAction"=dword:00000000
"AcceptRfbConnections"=dword:00000001
"UseVncAuthentication"=dword:00000000
"UseControlAuthentication"=dword:00000000
"LoopbackOnly"=dword:00000000
"AcceptHttpConnections"=dword:00000000
"LogLevel"=dword:00000000
"EnableFileTransfers"=dword:00000001
"BlankScreen"=dword:00000000
"RemoveWallpaper"=dword:00000001
"EnableUrlParams"=dword:00000001
"AlwaysShared"=dword:00000000
"NeverShared"=dword:00000000
"DisconnectClients"=dword:00000001
"PollingInterval"=dword:000003e8
"DisableTrayIcon"=dword:00000000
"AllowLoopback"=dword:00000000
"VideoRecognitionInterval"=dword:00000bb8
"GrabTransparentWindows"=dword:00000001
"SaveLogToAllUsersPath"=dword:00000000
"RunControlInterface"=dword:00000001
"VideoClasses"=""

=========================================

Save it as VNCset.reg

Now we need to crack open your boot.wim using DISM.exe for this (Search technet if you need to know how to use it) Then we are going to the startnet.cmd file to make it execute Install.vbs before the the task sequence prompt..  How to do this is already described well enough here http://technet.microsoft.com/en-us/library/cc766521(WS.10).aspx

Once you've set all this up boot up into youe WinPE and make sure the startnet.cmd files have run. 


you should then be able to use the TightVNC client to remotely connect to a machine running a Tasksequence through WinPE.. There are a few small problems though.. When booting into WinPE the Workstation (Computer name) is changed to something random..

A few solutions to the random computer name issue:
- Use BGINFO to tattoo the background with the temp computer name.
- Add a step that grabs the Pc name and e-mails it to an admin mailbox. (you can't use CDO for this you have to use a simple SMTP sender which  I may cover in a new post).

As per usual... if you find this guide handy please leave me a comment so I know it worked for you.

How to use a collection variable to prompt for a computer name during an OS Deployment Task Sequence in System Center Configuration Manager 2007

http://blogs.technet.com/configurationmgr/archive/2010/05/06/how-to-use-a-collection-variable-to-prompt-for-a-computer-name-during-an-os-deployment-task-sequence-in-system-center-configuration-manager-2007.aspx

Conflicting records in SCCM after re-imaging a system using PXE or DVD/USB

I've found that when if I re-image system that is already in SCCM a new record is created but the old record for the asset is not removed. Its actually very frustrating as it means that the wrong record can be put in a collection and therefore never work the way it was intended.

The duplicate/conflicting record doesn't appear if you re-run the task sequence the run advertised programs within windows.

What happens is when the task sequence comes up to the installing SCCM client it generates a new client ID which is why it creates a new record in SCCM. But the big problem is it doesn't delete the old record it just creates a new one with the same name but new GUID and ClientID.

I've been racking my mind for a solution to this issue. It turns out a earlier solution was almost in place I just needed to tweak a few things.

The solution I've come up with;

-Setup the Task System variable for OSDComputerName on the Unknown Computers collection

- Create a VB script that detects if this is a 'new' system or an 'existing' system. This can be done using a VBscript that checks if OSDComputerName variable is Null; if it is then we know it an existing system.

- If OSDComputername variable is Null then read the SMSMachineName variable and delete it from SCCM just before we install the client.

-

0x80091007 Task Sequence Failure.

This error was popping up on the failure on our main task sequence during the 'Setup Windows and Config Manager" section.

We had issues with the PXE Service Point Point the day before and had to reinstall PXE service Then upload all the now missing packages It turns out the SCCM agent package didn't update correctly on the distribution point.

'Refreshing' the package fixed the issue. Don't just 'Update' the DP as this just does a compare and uploads if different. Refresh copies all the files again.

If you are having this problem yourself i'd like to hear from you about it. Please leave a comment I might be able to help.

sources:
http://brothertu.blogspot.com/2008/09/error-hash-value-is-not-correct-when.html
http://www.deployvista.com/Blog/tabid/70/EntryID/62/language/en-US/Default.aspx

Roxio CD Creator 000D error

I had trouble installing Roxio CD creator on a Fujitsu Lifebook (e8420) it kept giving me "000D" error which isn't very helpful. Turns out the windows 'My Documents' folder was re-directed to h:\ and I didn't have a h:\ mapped to anything. This was the MSI throwing back a Pre-requiset failure based on it didn't have access to the 'my documents' folder.

Using the Subst command fixed the issue. "Subst h: d:\".

Wii Virtual Console issues on HD TV's in Australia (PAL users)

I recently downloaded Super Mario 3 for the NES on the Wii. No problem using it on my smaller TV but when it came to the 50" HD plasma it would display "Mode Not Supported" turns out that nintendo doesn't do 50Hz TV to well through component video.

We can fix  this by enabling "component video mode" in some games..

1. Go into the operations manual for the game. 
2. Then hit Z+A+2

more info here.

and here

Wii Component Cable Interlace mode
The mode can be enabled by accessing the operations guide of the game, and (with the Nunchuk attached) pressing the buttons Z + A + 2 simultaneously.
The mode can be disabled by using the same method, but with the button combination Z + A + 1 instead.
ref