WDS completes, no boot device on startup.

F1 to retry

You know the error screen.

Situation:
Dell Latitude e7440, solid state drive
Came with windows 8, used WDS to put vanilla W7.
W7 completes, but doesn't boot.

I went into BIOS, secure boot was disabled
UEFI was enabled, changed to legacy and it booted right up.

Also, with these e7440, I've been moving the SSD into the MSATA port.  I had an issue with one of the first e7440 that was losing the regular SATA connection, randomly.  I'd get the system and it would boot up, everything would be fine, I'd send it back to the user, it wouldn't work again.  The back panel is kind of flimsy, so I can only assume he was holding it toward the top, or the docking station was pressing against the cable causing the hard drive connection to come loose.

Move computers to groups in logmein central

Sounds simple right?  I was in Details view and for whatever reason I couldn't figure it out until I switched to List view.
I'm using Chrome to load the Logmein Central page.

Change to List view
Click the drop down by the computer you want to change and go to Properties
On this window you'll have a drop down for the groups you've created
Select the group and save

Moving a VMware machine from one physical machine to another.

First, SSH has to be enabled on each of the physical hosts.
on the VM host, hit F2 and log in.
Go to Troubleshooting Options.  I turned on both the ESXi shell and the SSH shell, then restarted management agents, I don't know if I had to do all that, but I did.
Once you've done that, go to your vSphere and go to the Configuration tab.
Click Security Profile under Software.
Click Properties under firewall, I put a check mark in SSH Client and SSH server.

This would be done on both physical servers.


I used Putty to connect to the server that housed the machine I wanted to move.  Once your connected, type:

scp -r /vmfs/volumes/(your datastore name)/(your VM host folder) root@ip.of.new.server:/vmfs/volumes/place/it/goes

It should then ask for the root password.  Those are not two separate commands, there's a space between (your VM host folder) and root, but it would all be on the same command.

SCP lets you move files, SCP -r lets you move directories, if you forget the R you'll get an error that its not a regular file.
I would also get "no such file or directory" the first couple of times I tried this, ESXi is case sensitive, so make sure you use proper case.

I also had issues finding out the path of my files.  To find out your path, go to your vSphere Client.
Click Configuration
Under Hardware, go to Storage
click on your datastore, this gave me the /vmfs/volumes/ part, the hex identifier can be replaced with the name you gave your datastore, this is located under identification.
You can right click the datastore, and go to Browse Datastore to see the folders that hold your virtual machines.


Also, in my environment I was only getting transfer rates of 4-5mbps.
This is on a gig network, with 10k SAS drives, transferring from a G7 to a G5 HP server.

**********
Also....

If you go have a big enough drive, you can copy the files to your computer, and then upload them to the other server.  This is the video that helped me.

https://www.youtube.com/watch?v=XSZdWQMynhw&index=4&list=PLe-uhdcSI8Z3FSPcGdUvnurCcGuW4vESm

*****************Update on transfer speed*******************
I was able to double the 4-5mbps by changing the raid of the target server.  I was running RAID 5, changed to RAID 10 and saw 9/10mbps,  So the limitation before was the Hard Drive speed, which makes sense and I should have known, but I guess I just took for granted.

Unable to update the IP address on Isatap interface isatap.

Environment:
ESXI 5.5
Windows Server 2012 R2

Error comes up when running DCdiag.

To clear this I went into Device Manager, show hidden devices, disabled and uninstalled the ISATAP connector.

Clean DCDIAG after that.

WDS capture, windows failed to start 0xc000000f

I'm trying to capture an image using WDS.

I went through the proper steps of creating a boot image and then a capture image.

The Boot image loads fine, the capture image results in this screen:

WDS is running on fully patched (as of 3/10/2015) server 2012 R2

After searching the internet and finding a number of people have this issue, some referring to KB2919355, I finally found a fix that worked.
(If you are wondering, no, removing KB2919355 and reinstalling WDS did not work for me.)

I used DISM to mount and unmount the capture image.  I created a "MountDir" folder on the same drive as the rest of the boot files.  In red are the variables for whatever you called your capture image.wim and wherever you want to mount it to.

C:\>dism /mount-wim /wimfile:C:\RemoteInstall\Boot\x64\Images\capture_x64.wim /mountdir:C:\MountDir /index:1

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Mounting image
[==========================100.0%==========================]
The operation completed successfully.

C:\>dism /unmount-wim /mountdir:C:\MountDir /commit

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image File : C:\RemoteInstall\Boot\x64\Images\capture_x64.wim
Image Index : 1
Saving image
[==========================100.0%==========================]
Unmounting image
[==========================100.0%==========================]
The operation completed successfully.


And that's it.  Mount it, do nothing to it, unmount it saving 'changes' and viola.  You can now boot to the capture image.