Monday, June 27, 2011

Unable to remotely manage Hyper-v from Windows 7 RPC - rpc server unavailable unable to establish communication between and

If you get this error when connecting to Hyper-V from a Windows 7 OS
RPC - rpc server unavailable unable to establish communication between Client and server
 Then you should follow these instructions.

First up, check you can start your firewall. If it's stopped and you get error 5 when starting it. Take a look at the below KB from Microsoft.

If fixed the issue for me and also resolved my Hyper-V issue.

Friday, June 24, 2011

Citrix EndPoint Query Writing. Values with spaces

I found the documentation for query writing for Citrix endpoint is actually quite confusing.

For example:
CLIENT.REG('HKEY_LOCAL_MACHINE_64\\\\SOFTWARE\\\\Microsoft\\\\Windows\\ NT\\\\Example').VALUE == 'Joejoeinc at home'

Would produce fail as there are spaces in the value

To write this query properly we actually need to tell the query window that we want to have spaces in the value. You would write the Reg query as so.

CLIENT.REG('HKEY_LOCAL_MACHINE_64\\\\SOFTWARE\\\\Microsoft\\\\Windows\\ NT\\\\Example').VALUE == 'Joejoeinc\\ at\\ home'

That's  "\\SPACE" between each word.

That to query a reg key that has a space in it like 'Windows NT' you need to write it like 'Windows\\ NT'

Thursday, June 09, 2011

VBScript Convert Date to String(text) / rename folder to foldername+Date

Dim MyDate
MyDate = Replace(Date, "/", "")

On error resume next
Set objFSO = CreateObject("Scripting.FileSystemObject")
objFSO.MoveFolder "C:\test" , "C:\test" & Mydate

Friday, June 03, 2011

Configmgr/SCCM, Abort PXE issue when attempting rebuilding a PC (re-run a TaskSequence)

Sometimes when attempting to re-image a system you can sometimes be greeted with an abortPXE error. This can even happen after you delete the record from SCCM. What's happening is the WDS/PXE service can be holding onto the record until the cache expires... this cache can sometimes take a long time to expire.

lucky for us since SCCM 2007 SP/2 We've been able to set the cache expiry from the registry.

On a x86 machine
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\PXEOn a x64 machine the registry key is under WOW6432NodeHKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\SMS\PXECreate a new DWORD value CacheExpire, and set the desired value in seconds. For example, if you prefer the cache expired in 2 minutes, set the value to 120. If the value is set to 0, then the default 60 minutes value is used.
Note: Setting the value in CacheExpire is only supported in ConfigMgr 2007 SP2.

for more information see

I found this can also happen if you delete the record from the system and the target computer is still on and operating before you shut it down. the client sends an update to SCCM before you shut it down.