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.
http://support.microsoft.com/kb/943996

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

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.

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

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

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

http://blogs.technet.com/b/configmgrteam/archive/2010/05/27/pxe-cache-expire-behavior-in-configuration-manager-2007-sp1-and-sp2.aspx

Notes:
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.

What's wrong with installing an MSI and a PATCH at the same time?

A few fellow SCCM Engineers have come across this issue. You're trying to install an MSI based application and apply a PATCH.msp at the same time. With SCCM this usually is met with error 1635 unable to locate the patch file. This happens because when you specify the patch the MSI installer doesn't know where the relative location of the patch file is (probably something  that M$ has to fix up at some point).

To get around this problem there are 3 general solutions..

1. Separate the install and patch process (i.e handle them in separate steps)
2. Specify the absolute path the to MSP (which can be difficult if you have multiple installer locations)
3. Create and admin point from the original software and then patch the admin point with the patch.msp. This way you don't have to patch anything when you install as the admin point has the updated files already.

Personally option 1 or 2 are the easiest for me.

More information is available on MSDN: [also you can see in the example they put the entire path.]
http://msdn.microsoft.com/en-us/library/aa370576(VS.85).aspx

Virtual Machine Connection Key Combinations with Hyper-V - Virtual PC Guy's WebLog - Site Home - MSDN Blogs

Virtual Machine Connection Key Combinations with Hyper-V - Virtual PC Guy's WebLog - Site Home - MSDN Blogs:

VBscript - How to obtain the local SCCM Proxy Point from WMI

Say you have an application you need to run from a share on local SCCM site server, not from a specific DP.

In this case it can be really easy to determine what your local site server is by querying local WMI for the MPProxy Point.


strComputer = "."
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\ccm")
Set colItems = objWMIService.ExecQuery( _
"SELECT * FROM SMS_MPProxyInformation",,48)
For Each objItem in colItems
Wscript.Echo "sitename: " & objItem.name
Next