The IT Crownd

Ran into an issue where I needed to "double-hop" from one PSSession to another. This led to an investigation into how to set up CredSSP My issue resolved around getting System Center Orchestrator to run some PowerShell which reports back the number of users currently on our VPN server. I followed the awesome posts from * where they suggest to run a PSSession onto the localhost (in my case Orchestrator) rather than to run PowerShell.  This is cool unless you then want to PSSession onto another box, in my case my VPN box to run some more PowerShell! The post does briefly mention setting up WSManCred - too briefly ;) Anyways on the first hop machine you need to run (as Administrator) the PowerShell - replace *.domain.com with you domain name - or for tighter security replace with the FQDN of the target server. PS C:\Enable-WSManCredSSP Client -DelegateComputer *.domain.com And on the second hop computer... PS C:\Enable-WSManCredSSP Server -Force At any time you

Had some trouble with our ESX VMs booting to the Windows Deployment Server when using UEFI. UEFI is now the default boot for VMs - finally! Changing the network interface from VMXNET3.0 to E1000e made things work again!  We had Secure Boot enabled in both cases. Our physical devices (DELL Latitudes) have no issue so we suspected ESX. Devices with VMXNET interfaces were failing to boot, get DHCP or anything....they just (seemingly) timed out. Turns out, for us it was a TFTP configuration. In WDS right click your WDS Server node and open the properties dialog.   GO to the TFTP config tab and set the following Disable : Enable Variable Window Extension Configure: Maximum Block Size to 16384 Worked for us. Thanks to fboehme (although I see Secure Boot is disabled in this post!) https://communities.vmware.com/thread/572481?start=15&tstart=0