fizban2

Sharepoint 2010 as well installed and looking cool

server 2003 like XP or Vista or 7 can RDP over the internet as long as port 3389 is not blocked by your coprorate firewall, if this is open you should be able to rdp to the machine as long as remote desktop has been enabled. a VPN solution would be safer for what you are looking to do.

this is not possible,

Using the built in firewall have worked very well for me, runs well and easy to manage

the batch file was calling the slmgr.vbs file http://ss64.com/nt/slmgr.html check there for more info on switches you can use to get the info you are looking for

launch a command prompt as an administrator (right click and run as admin) then run your imagex command. most DOS commands won't prompt for elevation.

Nobody an idea? 1. Windows 7 does use an XML file (autounattend.xml) you can edit this file within the WAIK which is free for download from MS 2. You don't have to resysprep your image unless you want to install applications prior to deployment. the WIM file is already sysprepped and ready to go. 3. you will want to use the Default profile for any changes you want to use for any new user to receive. the Default User folder is a redirct (symbolic link) to the default folder.

Luke, You are right, if the client is not in AD, then no GPO to turn on the NAP agents. If that is the case then the machine with be quarantined. The servers that are part of your remediation group will allow those machines to be joined to the domain (you have a RODC there) your DHCP server will still server the client an address, just will only allow routes to the servers in the remediation group. Once there you can join the machine to the domain and it can recieve the GPO. For future use, i would suggest turning on the NAP agents during an unattended build process, that way the GPO is only a fail back incase someone tries to turn of the agents.

blurb Microsoft Deployment Toolkit 2010 is the newest version of Microsoft Deployment Toolkit, a Solution Accelerator for operating system and application deployment. MDT 2010 supports deployment of Windows 7 and Windows Server 2008 R2 in addition to deployment of Windows Vista, Windows Server 2008, Windows Server 2003, and Windows XP. /blurb Microsoft Deployment Toolkit (MDT) 2010

Deploy Windows 7 and Windows Server 2008 R2 with Microsoft Deployment Toolkit (MDT) 2010 RC. MDT 2010 is the next version of Microsoft Deployment Toolkit, a Solution Accelerator for operating system and application deployment. Look for new features in MDT 2010 including flexible driver management, optimized transaction process, and access to distribution shares from any location to simplify deployment and make your job easier. Save time and money when you deploy faster and easier with MDT 2010. As a member of the MDT 2010 RC review program, you will be asked to provide feedback about the tools that the Solution Accelerator includes. If you are not a member, click Here to join the Beta program. For members, click here.

so we have RTM and RTM, if you check the event logs, what error is being dropped for the failed installation?

those are the RTM tools, but we need to know if you are running the RC or RTM of windows 7, check the dll cluberti listed and let us know the version, the RTM tools may not work properly on the RC version of windows if that is what you have installed

i would suggest deleting the virtual network and recreating it, i have flaky netowork issues before and deleting the the virtual NIC and recreating it as a last effort has helped.

could be in issue with the NIC being shared by both machines. can you add another NIC specifically for the VM's and leave the other NIC for the Hyper-V server it self

what is the format of the file after the sysprep occurs? i apologize, i assume that alteris was using a WIM file to push the clients machine. If alteris is not using a WIM you can do this: 1. extract the files off the DVD 2. inject the drivers into the WIM file 3. recreate your DVD 4. install your image 5. capture the image with the drivers.

if you are using a custom WIM you have created you can still use peimg (found in the WAIK) to mount the wim (imagex) and inject drivers directly to it. *example steps* Copy WIM from alteris location Mount Wim on in a folder you have created (make sure to use Mountrw) use peimg to inject the INF file and drivers for the SAS disk unmount and commit the WIM. test wim file with alteris and verify success

you are going to have to inject the SAS drivers into your wim file. that is the only way to be able to deploy to that harddrive

essentially yes, if you want to save DVD's, you can format a USB stick and place all the source files on that. You can then boot off the USB stick and test the unattended file. the WAIK comes with complete documentation on doing this

nope, i have 4 seagate drives and have had 0 issues with any build of windows 7, the early beta builds if i lost power unexpectedly would cause a rebuild of the array frequently but since RC had not had that issue

can you put up a pic of your task sequence with the steps where you are injecting the drivers?

i would suggest downloading the Windows AIK and using that to work on your image, much easier that way. If you are not adding any installed applications to the image you can used the sysprepped image that comes with retail disk. just pull the files from the disk, load up the WIM with SIM and create an unattended file with the settings you want, name it autounattended and add it to the files from the disk and create a new ISO.

if you are looking to make use of Multicast programming you may want to start here Multicast Programming http://msdn.microsoft.com/en-us/library/ms739172(VS.85).aspx

could you tell us a little more about your computer? are there multiple HD's? can you move the user data off to a DVD or external PC while you do the upgrade?

i am running 8.8.1009 on win 7 64 bit without issue, it should install fine for you

Jazkal is right, since it is only a 64-bit image, you will need a 64-bit PE image, which can launch a 32-bit image as well you will also need a PE 3.0 to launch it