Tripredacus

I think you need a 70% or higher. Just remember, more than half the exam is going to be simulation based, so first hand knowledge of Windows 7 (actually having used it) is going to be very valuable for you.

All say hi

Yes since vista if you have Autounattend.xml on floppy or usb thumbdrive windows will use it. I made a mistake of having an autounattend.xml and unattend.xml (with oobe passes) on the same USB key once, and kept wondering why the install was booting to the desktop and creating users, etc.

A sure-fire way would be to have it install the app as a First Logon Command, then you wouldn't have to worry about it.

Actually, if you leave the Computer Name node out of the Unattend file, it will prompt for Computer Name during OOBE.

It depends on when you install it. I've seen a system that had Chrome installed into the Administrator account while the system was in Audit mode. So after you sysprep and Windows disables the Administrator account, you can't access (or find) Chrome unless you take ownership of that account and/or re-enable it.

I'm running a 256MB 8600 Radeon in my Win98 PC and everything works with it. But I also originally tried a X1650 Pro 512MB card and worked on it a few days but no drivers would work for it. I tried the hacked ones too but got tired of getting the BSOD.

Well Server 2003 is a little more strict on the security. You'd find this out when you start trying to get files off the server from the clients. You should be using authentication on all the machines, although you could just turn on all the guest accounts but they are disabled for a reason. Since you are running a workgroup instead of a domain, you need to add the local account of the server onto the XP machines. So it would be SERVERNAME\ACCOUNTNAME. You could add this account into each of the XP Administrators group, or just into the permissions of the shares. This way, the Server would authenticate onto the XP machines and just have it remember the password. YOU NEED A PASSWORD, I do not think Server will let you log into a system using an account without a password. If this doesn't work out, you can create an account on each of the XP. They could be the same name and password. Then assign the rights for that account to the shares. If you try to access the shares, you get a credential prompt and type in that info. Usually for these remote access accounts, you do not want them to work like regular accounts because typical users won't be using them. So when you create them, uncheck "User must change password at first logon" and check "account never expires" and "user cannot change password" and you should be set.

Are you sure? I have Windows 7 Pro and can see AppLocker. Here is how to get to it: 1. Control Panel 2. Administrative Tools 3. Local Security Policy 4. Application Control Policies

I wonder where the Windows 7 total comes from. Do they take into account VLKs to the enterprise, COAs to OEMs and Media to disty? If so that means a lot of copies of Windows that are sold but not currently in use. I think it would be hard to figure out how many were actually being used because you can't just go based on the stats they get from activations, since you don't have to activate machines from OEMs like Dell or HP.

I've got a couple old ones hanging out on my email, like Sircam and Bagle, but they won't be any use unless you have an email setup that will let you receive them. I did a test to my work email, but our firewall stripped the virus out, and identified it to me as:

I honestly can't say for sure, as I've never tried it. However I did accidently leave a USB key in a machine that had an unattend file on it and Win 7 sysprep did use it. It was a head scratcher to start with. So it MAY be possible but I do not know if that was a fluke or if it would work 100% of the time. Basically, if you have the time, try it out and see what happens.

The best documentation you will find for Deploying Windows 7 is in the WAIK files. They are also mirrored on Technet, but for me it seems easier to find things in the WAIK CHMs than Technet. Here is the Technet dox for config sets: http://technet.microsoft.com/en-us/library/dd744265%28WS.10%29.aspx I've never made a config set for 7, I haven't had a need for them or seen a reason to use them.

So you WANT to get a virus? Seems weird...

My main gripe with these chassis is that either you end up with passive cooling on the CPU, or the CPU fan actually touches the underside of the PSU or HDD caddy. I have one of the larger ones here that has 3 hard drives in it too and I don't like that one much better.

I've installed the Recovery Media Creator before but I've never used it, nor determined how it knows if the discs were burned already.

In order to do this, you would have to customize your WinPE and get the syswow or Win32 subsystem support into your PE. Or you can just do what I do, use x86 WinPE for systems that need 32bit software functionality.

Wow that is definately way too long. The longest I've seen was 5 minutes, but that is because there are a lot of programs installed. I do know of a sysprep delay issue with an updated IE installed but I can't seem to find it. You should look in Panther to see the log file, maybe it is encountering some problems (warnings) or it could be you just have a lot of files or programs installed.

A similar question was brought up here:

This can't seriously be "new" can it? Conficker used this vulnerability in version 2...

Welcome to the MSFN! If you are going to post trial software, best to link to the official website: http://www.quetek.com/prod02.htm

Welcome to the MSFN!

Whether it is normal or not, who can say. I would say that I never like the idea of using a glue gun inside a computer, but then again I am also not fond of the form factor arrangement that Shuttle uses. That wire on the top, looks (the picture is blurry) that it may be a 4pin that a floppy drive or some video cards use. If you do not have a floppy drive, that may be why it is not connected to anything. Here is a picture of what I mean: http://www.playtool.com/pages/psuconnectors/floppy.jpg

WDS does not natively support Windows XP. Are you using mixed mode and RIS for XP?

Sorry I didn't get a reply in before all these others. Yes there is a way to do it. Try these steps out: 1. Deploy the image. 2. Take the HwID and search the INF folder for it. The file you are looking for is OEM*.INF (where * is a number) 3. Mount your windows image 4. delete that INF file from the stored image (verify it is the same one, should be, but best to be safe) 5. Redeploy. That SHOULD do it. I've had to do that in the past after accidently injecting the wrong drives into images. Had to find the INF name and take it out. This is the manual way, and only way to take drivers out of images if you didn't use DISM to put them in there. Also, deleting the INF will stop the device from being installed, but its support files will still be on the system but that shouldn't be a problem.