ChrisBaksa

Member
  • Content count

    230
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ChrisBaksa

Contact Methods

  • Website URL
    http://
  1. Have you tried Daemon Tools? http://www.daemon-tools.cc I know it works under Vista and is 64 bit compatible. WinRar will also open an ISO. Chris
  2. Thanks. That is what I was hoping for. Chris
  3. I'm sure you already thought of this but I'll throw it out anyway... Do you have any other account with admin level privileges that you can log in with? You can then change the admin Password.
  4. Hello All, I have a scenario that I'm toying with and I'm trying to get some answers as to what the final outcome will be. let me first set the stage. I have not actually played with Hyper-V yet which is why I am asking these questions and I have no way to actually test due to lack of hardware. I run a dell Poweredge 2950 (72 gig mirrored boot volume and 146 gig x 6 Raid 5 volume for data). It has windows 2003 R2 64 bit installed and VMware Server Ver 2. I run 3 VM's on this box (DC, Exchange/Web, App server). The Host itself also acts as my file server. The Raid 5 Data drive contains all the VM files as will as all my Media, Application library, User data, etc... I also have 2 external USB/Firewire mass storage devices attached to this box for addition storage and data backup. With that said, my plan is to rebuild this box with Windows 2008 and Hyper-V. I would build a temp box and move my VM's to it while I rebuilt the Dell with 2008 and Hyper-V. This way my environmet would still be up and running. The Raid 5 data drive would remain intact with all it's data. I would then convert my VMWare VM's to Hyper-V VM's. So in theory, when I install Hyper-V the host OS now becomes a "virtual" but is still the Controll OS. My question is... Will the Control OS still see the Raid 5 Data volume as it did before I installed Hyper-V? Remember I used the Host OS (in this case the control VM) as my file server. I would simply reshare/repermission my data at this point and I'm done. But if the Control OS does not see the volume as it's own, I loose the functionality that I had and I waste alot of high performance RAID disk space. This is why I dont want to install VMWare 3i. I would loose all the space that I currently use as a fileserver forcinng me to move all that data to an external (slow) storage device. Does anyone know how this will play out? The hardware is fully capable of running a Hypervisor, and my end goal is to do just that. What I dont want to do is embed all my file server data into a VM. If I have a problem with the VM, I'm screwed and teh data will most likely be lost. But if the Machine will not boot for what ever reason, I can boot off a pe disk and get my data. What do you think? Thanks in advance Chris
  5. Thanks Br4tt3, I am finding that alot of people are not using any of MS's tools (like the MDT). I've been in contact with MS as well as several other individuals in my situation and the Unattend.xml is simply generated line by line and checked against the WAIK before the code is rolled into production. One company I spoke with is using a generic unattend.xml and is doing a search and replace for strings. Chris
  6. Ok.. here is the big question. First let me describe my process. I PXE boot to WINPE... I Partition and format drive... I Use ImageX to deploy a custom Image (I used the Sysprep /OOBE /Generalize /Shutdown switches and then created my image) I Now I copy my PNP drivers to the drive (unattend.xml has the locations in it) Now my Unattend.xml is created via scripting and has my regionalization, IP address, pnp driver paths and other information. What do I do with the file? Does it get rename? Where does it go so when WInPE rebots and teh host boots up it is used and builds with those settings? I assume it has to be placed somewhere on the host's hard drive. But where? I can't find this information anywhere. Thanks. Chris
  7. MDT? Please elaborate. Chris
  8. I was wondering if anyone was dynamically creating the Unattend.xml for their Windows 2008/Vista installs. I'm looking for information on how people are creating the unattend.xml thru scripted methods. Specifically... I'm looing to do this thru VB Script. It seems Micosoft has made this process a nightmare. The old Unattend.txt was easy. Aything helps. Chris
  9. Same exact situation here. I can use a stand alone PE cd that prompts for input or I can build via winPE pushed from a PXE server. You enter the information on a web page and it gets stored in a Database. Once PE is loaded, it collects the data from the DB. The same scripts support both building methods. I support 52 server models across HP, Compaq (legacy boxes) IBM, Dell and Vmware. Chris
  10. I figured it out... Need more coffee. Chris
  11. Has anyone experienced a problem running imageX.exe from within VB from PE 1.6? I have a VB script that is "supposed to" lay down the WIM image. But when I call the exe form within VB it totally ignores the commad. I've echoed out the command line and it is good. and If I run it manually on the command line. It works. Chris
  12. Has anyone integrated the Windows 2008 6f bit Hyper-V nic into WinPE 2005 (1.6)? I'm having a bit of trouble finding the correct driver. 32 bit works fine. 64 bit is my issue. This is PE 1.6 not 2.x Chris
  13. No. We wrote a syncronization tool that much more powerfull than dfs. We do have DFS integrated in the firm. But the the OS builds work in a very controlled manner. Development, Stageing and Production locations globally. A bad package could blow up a traders box and loos the firm money. Very tight change management. Chris
  14. i like to think it is efficent single image to to run every model of server that i manage around the globe, and since there is compression on the wim you save space vs have them on a share someplace, that share is going to have to replicate or copy so bw savings are minimal but that is another chance for errors in communication or transfer. hopefully i don't sound like an arse, just letting you know what we do currently, using a standard wim file with all drivers inject for the model servers we support (6 currently, all from HP) that build is replicated along with applications and and anything else needed globally via dfs to 43 different locations where we have sms server. from there the build can be run through WDS on any PXE bootable server. the build currently gets sequenced through the microsoft deployment toolset so we have mutliple install roles availabe depending on when the server roles will be. i have one build here in HQ that is our master or "gold" image that when we need add new drivers or replace old driver i open the wim update/remove drivers, then set back in the dfs share. through the power of dfsr, we replicate the bits that change and now have updated images. just the way i go about managing our image. it works great for our situation and i thought i would share what we have done with it! I'm not doubting your setup. However my change control process would not play nice with this. We have a weekly sync schedule where my changes are synced to about 40 distribution points around the world from a master location in the States. The Wan Traffic generated by the WIM files to Europe/Tokyo/India is very large in that model. And thats just the WIM files, The application packages also get synced during that process. My design is to leave the WIM files unchanged (for the most part). This reduces the need for those large transfers. My front end will have choices for the roles and the XML file will be dynamically built based on the selections (stored in a DB for one click rebuilds) If you think about it, the Master image really only needs to be able to access the disk. Everything else is a plug and play discovery of drivers. By keeping the drivers seperate in a file structure, I have the ability to copy only what I need. Nothing more. Syncs are much smaller and faster and I have the ability to version the drivers by hardware model. I have run into instances where one driver crossed Manufacturer platforms and was incompatable eventho it was the same model/partnumber. Thinking outside the box... the driver file structure I maintain also servers for other applications. P2V, V2P, BareMetal restore, etc... By pointing these apps/processes at the file structure, they can use the same production drivers in their discovery. This way I know exactly what driver is certified by me to be used in our environment. My 2003 Build support 49 models of hardware across 5 manufacturers. The 2008 build will start out supporting about 5 models. Chris
  15. the preferrable path woudl be to inject your drivers using PEimg into the WIM file you will be using check out the WAIK at microsoft downloads Preferable. Maybe... But not very effecient or manageable. In a large Enterprise firm, It is much easier to keep the drivers seperate (out of the WIM) and copy them when needed. Most of us have a process to copy only the necessary drivers based on teh Hardware. This will allow your Gold image to remain unmodified thus saving larger ammounts of data having to be copied to remote locations (across the WAN) Driver versioning is easier and the WAN traffic is reduced to the drivers that changed not the entire WIM. The cost of the process is an addition reboot as you prep the host to use the newly copied drivers. Chris