fizban2

Hyper V will use the drivers on the Host OS for Virtualization aware OS's (Currently Vista and Server 2008) older OS's like XP and 2003 will use still use legacy emulated drivers

what are the plans for the Server? What Role is it going to play in the environment? What applications and depedencies is it going to have? lots of questions to ask also i would worry about using this server if it is not going to be approved for 2008. That means you are going to have to fight drivers that aren't validated for 2008 and with the re-designs that happend you might be causing yourself more hassle then it will be worth

your best bet is to use Process Monitor, it will give you an excellant understanding of what is happening when your machine boots up

I believe that the newest version Ghost would allows this. I would ask though why you do not use the WAIK and the WinPE to create a WIM file for Vista (since this is the format used now)

Right click on the Documents (D) name on the start menu and choose Rename. Change the name to what ever you wish!

as a replacement for ghost you might want to look at the Microsoft Deploymeny Toolkit. It is free and will work with WDS for you to deploy XP, Vista, 2003 and 2008. you can add applications, scripts, drivers etc to customize your image as nessecary. We use RIS now and are in the process of configuring our 2008 and Vista Images on MDT and SCCM (System Center Configuration Manager) to deploy Applications and post installation modifications

it is not the hard drive you need a driver for, it is a controller that connects to that drive. http://support.gateway.com/support/drivers...&dscr=Intel SATA/Mass Storage Controller version: 7.0.0.1020 this looks like it is the HD controller you are using, you will have to either intergrate the driver into your XP image, or add the driver via a floppy disk during installation

going to need to re-install the drivers from ATI

double check the Windows Experience rating and verify that Aero is enabled in Windows Color and appearence (right click on the desktop and choose personalize)

i would take it back, he is not going to have a very good experience with it and probably will not well everything he needs (unless he plans on surfing the web and that is it, even then i would bet it would be terribly slow).

Using WDS with the microsoft deployment toolkit will get you what you want

Happy Birthday Zxian!! hope you have an excellant day!

Well, it works great for us here when the base PC is an ACPI PC. i think we all agree the script will work as anyone who is updating their HAL in their XP image is doing the same thing, Iceman was just pointing out the specifics. back to the original post, Go download the Microsoft deployment Toolkit and the WAIK, you will be able to create both XP, 2003, Vista and 2008 based images from that tool, it will also intergrate into SCCM if you are looking to move to that from SMS

the problem isn;t that XP won't detect the wrong HAL, the issue is that after you ghost a machine it has already selected the HAL it will use during install and won;t change unless you manually do it (even with sysprep) say you build and test on a single core machine and puch it to a dual core machine, only a single will be used. vista doesn't have this issue as it is HAL independent.

try reseting the FSRM Click “WinKey” on your keyboard. Type “cmd” and hit Ctrl+Shift+Enter. That will bring you to the command prompt in Administrator mode. It you still have UAC enabled, it will ask you for permissions, click “OK”. Navigate to your Vista system folder (i.e. C:\Windows\System32) Type “fsutil resource setautoreset true C:” assuming that you have your Vista on drive C. Reboot.

i thought VMware server 2.x ran on apache? do they have an IIS7 version now as well?

Check out sites like www.zipzoomfly.com, www.newegg.com, www.froogle.com. Bestbuy is ok if you have to have it that day, but for the best deals the internet is the only way to go,

Real quick, do you know the speed of your ram (Mhz) and your HD's(rpms)? sounds like you are having bottle necks at one or the other. recommendations would be to check out the reliability and performance section of computer management, start a MP3 or Video and check out this section and you should see what is causing you issues

Webcasts, books, and just live testing are what i have always done, build a 2008 lab, even better build it at home and run your house on it, forces you to learn it and if it breaks to fix it, labs can be easily ignored when a problem arises. there are several microsoft learning tracks you can check out at http://www.microsoft.com/learning/default.mspx Not looking for "track" options, I've always prefered (my own) self study pace, I've no interest in classrooms, & I detest boot-camps, brain-dumps and the id10ts they tend to produce. I'm currently running 5 2k8 servers via VPC 2 RC0s (one core), 2 RC1s, and 1 RTM. I also plan on migrating 2 of the 3 physical server in my (home) lab to 2k8 as soon as time permits. Fun Read? I need information not entertainment... (Details man, I want details) ...Not the high level fluffy stuff (I leave that for the sales monkeys & talking heads). Right... been at that for many years already. The company I'm with does 24/7 server management contracts, so I work frequent 16 hour days, nights, weekends, and holidays. I'm not some green punk kid straight outa college ... I'm also not (stupid) cocky enought to think I can pass the thing with my eyes closed (rust forms quickly at my age). I'm just looking for some kind of heads-up on what topics they're planning to grinding on this trip through. Like 70-292's (suprise) beating on WAN level DNS configurations throughout the entire test (which I did pass the first time). The ExamCram that I had depended on in the past series (now ExamCram2), has completely gone to hell IMO so I'm looking for a proper alternative. $100 bucks is $100 bucks Ya know... just finsihed the 70-648 MCSA migration to 2008 AD related was still heavy on DNS (GlobalNames zone) , AD LDS (light weight directory services) AD FS (federated services) setting up Networking was all about NAP, the new RRAS setup using SSTP vpn for vista SP1, Server core installations, NOTHING on Hyper-V be prepared for Virtual Server 2005 R2 questions though. i used some tests from measureup.com they worked out very well and for 55$ it seemed a good deal passed so it is justified for me

moved to the vlite forum

the Names and Comments fields can both be populated in the active directory users and Computers tool, you don't have to go to the Domain Controller to do this the tool can be installed on your machine via the windows Server support tools. from there you can see the AD design for you domain and can search and edit machines to add comment information. the name information for machines is populated based on the machine name, this can be edited if you change the name of the machine.

The anwser to the original Question has already been found, the issues with his installation of vista were realted to the nlite intergration of SP1. closing topic

Installing Vista on the machine then installing the service pack has no issues, either from the full SP or from Windows Update. Using an intergrated Vista SP1 intergrated disk (already intergrated from MS) has no isues either. I agree there should be a way to slipstream an SP into a image for those who want to do this to keep their images up to date. I would bet at some time the WAIK will be update to do this. for most people though, downloading the ~48 meg update from windows update will be the easiest solution (when i say most people i mean non computer people ) what is the FSB on the Celeron? 533? how fast is the ram?333, 533, 400? how fast is the HD? 5,400rpm? 7,200rpm? the machine for the most part meets the minimum requirements for Vista (depending on what version you are running) 512 of ram is the absolute minimum you can use and even then you are going to run into troubles. even with a gig of slow memory you are not going to get good preformance. Sadly automation is what the masses look for, they don't want to have to enter every setting and adjust every value to get their computer working. they just want to get their computer and have it work. The very small number people who know every setting they want to configure is not Microsoft's target audience, the business and consumer markets is what MS aims for, not the enthusiasts. If you install vista RTM, then upgrade with SP1 from the full install or Windows update it is going to work. By chance it does not work, you will get logs that can looked to find out why your installation failed. Since you have edited to consitancy of the orignal files now windows cannot tell you what error has occured because it is not expected. windows expects files to be there and when they are not there, or are changed (vlited) then you lose that ability to troubleshoot the problem. My installtation of Vista 64 bit SP1 took about 15 minutes to install total, this was from putting in the DVD to entering my username and password. You are right though, they should released tool at the same time as launch for SP1 to intergrate into the image, granted that they redid the entire imaging process i am sure this is still being looked at as the SP has to be able to examine the image it is intergrating into and check for how many images are on the WIM, what versions they are, and then intergrate based on that. Not as simple as it was with XP. Give it time and i would be the WAIK will be able to intergrate at some point. Again installing Vista RTM, then installing the Service Pack results in no issues or issues that can be troubleshot. Again problems occur when you alter the OS in way that it is no longer able insure it's integrity. When you start altering your OS you do that with the knowledge that you are possibly setting your self up for issues in the future releases. To each his own with what vista should come. Seeing as at work we deploy a vista image internationally i enjoy the fact that Language and speech supports are already there for us to use. it makes our job much easier.

So you slipstreamed the full Vista SP1 into an RTM build (not recommended, use WU or a SP1 intergrated disc) and removed pieces of the OS and installed it on a machine that barely qualifies for that OS's requirements and you are blaming the OS?

Thanks for the feedback. I did some digging last night and it apears I have an F2 based CPU and Gigabyte has not yet released a BIOS that supports F3 Stepping for my current CPU. Since it will be a while before I can get an F3 CPU or a new Mobo. I am looking at other options. A Thought, workaround for Hyper-V on non-F3 BIOS,CPUs. What about Installing Server 2008 Core and have something like VMWare Server v2.x or VMWare Workstation v1.03 ontop of 2008 Core? That would kinda serve the same purpose wouldnt it? I mean I know it would not beusing Hardware based virtualizing in the same way as Hyper-V would but It would almost be the same thing no? Any thoughts? Thanks for the feedback! Mr the problem is VMware products are not made to work on Server Core, most of the products still require portions of the GUI to manage and run those Apps. If Vmware releases a version that is more like its ESX version where a GUI is not needed, then you would be set. till the you will need to run a full install of 2008 to install VMware products