ScottV

Well, I essentially am by not configuring anything... i.e. Choosing to make the disk "Make Known Good" or "JBOD". The state of the disk is either/or when connected to the RAID controller. I'm not trying to configure RAID 0 or RAID anything... I tried to use settings that essentially just take it as blank/stock/no config and I get the same result. Very strange.

The P700 is similar to the P500 in that the Hard Drives are located in carriages at the bottom of the case. Behind the carriages, on the motherboard, are built-in data/power connectors for any size or type of hard drive that would sit in the carriage. As most I.T. folks know, SSD drives will position themselves differently vs. the traditional hard drive. I only have a single, 500 GB, SSD drive in the chassis. In the RAID configuration utility (from inside the computers BIOS), you can configure the disk as a JBOD or choose "Make Configured Good" (which I believe you would use if you were using RAID 1 and needed to make a Hot Spare). Whichever one I choose, I can image to the drive but it will never boot to the drive when the PC comes around for that to first occur. I'm not seeing anything in the RAID utility to make partitions or anything, just the disk configuration. I can immediately take the disk out of the carriage and have it go into a normal SATA port and it will boot right up and take off.... so Smart Deploy is seeing the disk, imaging to the disk, but somehow; the drivers for the RAID controller are not put into the image to make it bootable through the RAID controller. I concede that there may be more settings in the RAID controller that I may need to mess with but I can say that I've made a couple passes at it and nothing jumps out at me as something that would affect boot up like this.

I'm testing Smart Deploy against a Lenovo P700. I use a WDS server to deploy images. I use Smart Deploy in a production environment against several Lenovo models. P500's, W541's, W700's, S20's, S30's, T520's, T530's... you get the point. All work great. This P700 has a built in LSI RAID card that the Hard Drives plug into. The Smart Deploy wizard sees the Hard Drive at the beginning stage of deploying the image, sends the image to the Hard Drive, and then applies the Platform Pack. But after that first stage, when the PC reboots to first Start Windows and detect hardware and drivers, it says it there is no bootable device. I can immediately switch the hard drive to be connected to the SATA port and it will boot and begin the hardware discovery and the rest of the Smart Deploy process as usual. I have tried configuring the RAID and seeing if there are any settings that would affect this but nothing jumps out at me. It's configured as the BOOT device in the RAID config and it's a JBOD. Any advice? Is the RAID an issue with Smart Deploy?

I sent you an email with the files requested except c:\platform\dism.txt. It does not exist.

I had issues with a Lenovo Desktop that used a SCSI controller and it wouldn't work with them. Not sure if that is any help to your situation, but just thought I would add my experience.

I am trying to deploy an image to a Lenovo T520. I have the latest client (1.1.5010) and I downloaded the latest .PPK for it (Dated 7/8/15). The deployment process kicks off just fine. The client recognizes the model of the laptop and deploys the image to the machine (using Windows Deployment Services). It gets through the image deployment, and gets through the Windows 7 Setup (x64) screens but when it gets to the very first time the desktop comes alive, the automatic login to the network that kicks off a post_install script fails because NONE of the drivers have been installed for Windows (No Chipset, No Video, No Network, etc....). I use this same process for several other Lenovo models.... S20, S30, W530, W540, W541, W700, W701, M91P, T500, P700.... ALL WORK GREAT. Has anyone imaged this model and had this issue?

I have created a new image for Windows 8.1 using Smart Deploy. Everything works great and this image works on 3 models of Lenovo with no issues. I did this mostly as a test in the environment I'm in because Windows 8.1 is not used on the production computers. After getting the basics down, I discovered that the machines that are EFI-aware, are not activating Windows 8.1 because the proper partitions are not installed. See this link for what those should be: https://technet.microsoft.com/en-us/library/hh825686.aspx I'm not sure how to use VirtualBox to setup a Windows 8.1 image that will install on a EFI based computer/laptop that will automatically activate Windows 8.1. Could someone provide guidance?