Jump to content
DeployCentral

Erik

Administrators
  • Posts

    145
  • Joined

  • Last visited

Everything posted by Erik

  1. Hello Paul, You can give the information here a shot, it should get you up and running with the UK locale. Thanks! Erik
  2. Hi Jesse, Depending on your virtualization software you can use a number of different options. Cloned VMs: Install Windows 7 and the applications/settings that are common across all configurations to one virtual machine. Once you have the base line create clones of this VM so you do not have to reinstall Windows and the common applications for every configuration. You can then make your changes and capture the images. In this scenario you will use more disk space as you have one full blown install for each configuration but it is much easier to manage and capture. Snapshots: Most virtualization products allow for the capture of snapshots, or a place in time restore point. By utilizing these you could create the base installation, snapshot it and then continue to build your first configuration. Once complete you can revert to the base snapshot and continue to build your second configuration. Once they are all complete you would apply the snapshot for the configuration you want to capture then run the Capture Wizard. The caveat with this is that capture will need to be done by booting the virtual machine to the SmartDeploy boot environment so the correct configuration is captured. Differencing Disks or Linked Clones: Differencing disks and linked clones basically work by referencing a base disk that would be the base line installation of Windows 7. They are a bit easier to manage than multiple snapshots because they are logically separated. In this scenario you would still need to capture the image form the SmartDeploy boot environment. As for differencing images, they are intended to keep an image up to date over time by creating a smaller update file rather than recapturing an entire WIM. You could create differencing WIMs off of one of your base installs but I would suggest creating a single combined WIM instead. When you create the combined WIM (done by specifying an existing WIM in the Capture Wizard when capturing a new configuration) you will see multiple entries in the image name drop down when selecting your image from the Deploy Wizard. You could then have all the configurations in one single WIM and simply change the drop down to deploy the referenced configuration. Thanks, Erik
  3. It sounds like it could be something to do with the SmartVDK driver. You can go to Device Manager, Select View, Show Hidden Devices and then locate the SmartVDKSrv under Non-PNPDevices. Once you locate the driver right click and uninstall it. Reboot the machine and try to run the Capture Wizard again. Let me know if that works out for you!
  4. Yes, you can make that work. First you would need to create a VM with the OS installed to one partition and then capture that image. Be sure not to create the second partition in the VM. When you go to deploy the image select the Wipe and Load deployment. This will wipe the first partition that is targeted by the image and leave the second partition intact.
  5. Sorry to hear that, if there is anything we can do to help you out let us know. On the Platform Pack ground, both the DX7500 and 6000 Pro packs have been update. Please let me know if you continue to have network issues in PE.
  6. Hi, It could be the network driver in the Platform Pack. Are you only experiencing this problem with one machine type or multiple? At any rate, you can send in a request to support@smartdeploy.com and they can check out the pack and see if it is causing the problem. Thanks, Erik
  7. Hello Cory, The reason the answer file will not work is there is not USB 3.0 driver support in the boot environment and the answer file cannot be processed because the disk is not detected. To get pass this either use the USB 2.0 port for imaging purposes or add the USB 3.0 drivers to the Windows PE node of the Platform Pack. To add the drivers to the Platform Pack you will need to obtain the driver from the manufacturers website. Once you have the extracted driver you can right click on the Windows PE node of the Platform Pack and select Add, browsing to the folder that has the drivers. After updating the Platform Pack recreate your media and you should be good to go. Thanks Erik
  8. Hi Cory, I would suggest going back through the Deploy Wizard and mapping the network drive (on the image selection page click Browse>Network). Once the network drive is mapped and credentials are added you can export the answer file. The answer file will automatically reconnect to the network drive using the credentials supplied. The credentials are saved in the answer file but are not in plain text. Thanks, Erik
  9. Did you check the things I mentioned above with the mapping of the network drive to \\servername\reminst the image path to z:\images\[image group]\image.wim and whether or not the multicast transmission exists? If all of these things look good can you send the deploy.log from x:\windows\temp and the answer file that you are using off to Support@SmartDeploy.com so we can have a closer look at them.
  10. Hello, This error is generally raised when the namespace is incorrect. This can be caused by the network share you are selecting the image from not being mapped to the default \\server\reminst WDS share. You would then select your image file from the z:\images\[image group]\ folder. It could also be that the image doesn't have a multicast transmission setup. Please check both of these things, you could also try to restart the WDS services or reboot the server. Thanks, Erik
  11. Hello There, It looks like the problem is caused because the .cmd script is running with the 64bit command prompt. As the SmartWIM.dll that is in the installer form SmartDeploy.com is 32 bit you will need to use the SysWOW64\CMD.exe. In your script you could simply change SmartWIM.vbs to run as "C:\Windows\SysWOW64\CMD.exe /c cscript.exe [path to SmartWIM.vbs]". Alternately if you would like to contact Support@SmartDeploy.com we can get you a copy of the 64 bit SmartWIM.dll which you can register and run normally. Thanks, Erik
  12. This problem has been fixed in version 1960 of SmartDeploy which is now on the website for download. If you continue to have problems please let me know. Thanks, Erik
  13. Hello Ewen, It sounds as though you are doing everything correctly. This may be a problem with the new Silverlight version of the Capture Wizard. Can you please try downloading this capture.exe file and pasting it into the SmartDeploy install directory. You can then run it from there and test the WDS Multicast check box. Please let me know if that works or if you run into any problems. Thanks, Erik Note: With version 1960 and above this is no longer an issue.
  14. Hello, This is by design. The check box that you see with a Windows 7 image is to remove the System Reserve partition. Once the multicast deployment takes place the System Reserve partition is replaced. In the case of Windows XP there is only one partition so you can just capture the image as normal. Please check out this link for more information on multicast. Thanks, Erik
  15. Hello, It looks as if sysprep is causing the problem. Once run the driver that is associated with the root\vclone device no longer works and you end up with a SCSI RAID controller device that doesn't start correctly. To fix this you will need to reinstall the filter driver that Virtual ClonDrive uses. Please follow the steps below to do this. You need to get the Virtual CloneDrive filter driver; by default during an installation it is unpacked to the %temp% directory. To get the driver, start by installing the Virtual CloneDrive software on a computer. Once completed do not close the installer, instead select Show details, this will show you the install log. In that log is the path to the extracted driver. Look for Extract: VClone.sys and the output directory. Navigate to this directory and copy the files to the c:\drivers folder in your image (note the folder can be changed just be sure to update the path in the commands below if you don't use c:\drivers). Next capture your image with Virtual CloneDrive installed. Boot to the SmartDeploy Boot Environment (SmartPE)and select Deploy an image... Select Advanced Select Tasks From the Tasks tab create select Add Change the Phase to First Boot as System and the command to "c:\drivers\devcon.exe install c:\drivers\VClone.inf root\vclone" This should fix up the Virtual CloneDrive driver that's giving you the problem. You can test this process in the computer that has already been deployed to ensure that it works correctly for you. Thanks, Erik
  16. Yes, you can update your virtual reference machine overtime, however you will need to account for product activation. Depending on the licensing model that you company uses the manner in which you accomplish this could vary. I would suggest activating the virtual machine if you intend to use it and update it overtime.
  17. It looks like the task is starting properly however the script is running into an error. The script is failing to load the node for the InputLocale. Are you deploying Windows 7 and does the script look exactly like it is in the previous post (sometimes copying can cause odd formatting)? If both of these things are OK please try running the Deploy Wizard in a no reboot debug mode. This can be done by opening a command prompt (Shift + F10 from the main screen) then typing Deploy.exe /noreboot. Now you can go through the deployment as normal, after complete try running the script directly from the command prompt and see if you receive the error.
  18. Hi Tom, It sounds like you guys have done quite a bit of work getting OSD all setup. To answer your question, yes, SmartDeploy will integrate with SCCM. We are also a part of the Microsoft Systems Center Alliance. At this time the integration is more a manual process which will require you to import a SmartDeploy specific boot.wim to SCCM then create a simple task sequence to run SmartDeploy. This will allow you to keep the flexibility of image distribution, collection targeting, as well as any custom settings in your task sequence while using SmartDeploy to apply the image to the end point and inject the drivers. There is a guide that details this process located here. Thanks, Erik
  19. Hello There, Yes, it is possible to image a computer over the network. The easiest way to do this with out further setup is to simply boot the computer with the SmartDeploy boot media created by the Media Wizard, either CD/DVD or USB and then connect to a network share that contains your image. If you would like to add additional infrastructure to the picture you can setup PXE boot. SmartDeploy uses Windows Deployment Services as a PXE boot provider. There is some more information on this setup, as well as using multicast here. Thanks!
  20. Hi Dewin, Could you please try and run the task using cmd /c %SmartDeploy_media%\z\name.vbs and let me know how it turns out. Thanks, Erik
  21. Assuming it is on the root of the drive you booted to SmartPE with, then yes it should work.
  22. For the phase of the task you will want to specify after image is applied. You can prefix with cscript.exe or wscript.exe, or just put the path to the script, all should work. When booting %SmartDeploy_Media% is set as an environment variable that points to the boot device, which you can use to specify the path to your script. The [AnswerFolder] variable is essentially the same thing but will not work when calling a task. Thanks, Erik
  23. Good question, T:\ is actually set by SmartDeploy after deploying the image so it will not need to be changed. We assign S:\ to the 100 MB Windows 7 Boot partition (System Reserved) and T:\ to the actual install of 7.
  24. Do you receive any specific error? Like unable to locate the network path? I would check that simple file sharing is disabled on the XP machines, and that Windows 7 machines are on a network identified as a domain network. You might also want to check the advanced sharing options in Windows 7, this and the network identification are found in the Network and Sharing Center. Other than that maybe see if there is a firewall blocking anything. If you are still having problems you can send us over the netsetup.log from c:\windows\debug and we can check to see if there were any problems in the domain join process. If you need specifics on how to change any of the sharing settings listed above let me know. Thanks, Erik
  25. I have never come across this before, is the machine being added to the domain and is the domain admin listed as an administrator on the computer you are trying to access? Thanks, Erik
×
×
  • Create New...