ces973

Does this seem more like a firewall issue? We are seeing the same thing with 1709, but we have a DELL SonicWall for our firewall. Didn't see any of these issues in 1703, though. I have had engineers from Microsoft Premier Support working on this for the better part of 3 weeks now with no solution in sight.

We used to put SEP11 on our images and never had an issue with it. Some of our images were over 6 months old and it just picked up the newest definition off the SEP server whenever it first connected.

We're using WDS, but have it set up a little bit differently.

We had to enter a PowerShell command for ours to join the domain... shutdown /r /t 15 3 net user Admin2 /delete 2 C:\windows\system32\windowspowershell\v1.0\powershell.exe -command "Add-Computer -domainname DOMAIN -cred DOMAIN\Account" 1 true It asks us to join the domain right after it first boots into the 'Admin' account. The 'Admin2' account is just a junk account because you HAVE to create one in Win7. It then reboots 15 seconds after entering the domain credentials. Hope that helps some.

You can actually have it prompt you for a computer name, and then in the oobe System phase run a powershell command to have it join to the domain, all it will ask you is for a valid PW. This is how we are currently setting up our Win7 PC's. C:\windows\system32\windowspowershell\v1.0\powershell.exe -command "Add-Computer -domainname xxxx -cred xxxx\administrator"

I'm with FN-GM, not many of our PC's have more than 4GB of RAM. I tried putting 64-bit on a 1GB laptop, and when I saw the memory overhead was 800-900MB just sitting at the desktop, I decided to throw another GB in. That, coupled with driver compatibility and I think 32-bit will be just fine for right now.

We had this problem because we had force classic start menus enabled in GPO for our XP clients.

Nice! You're right, you cannot put this out to users if you already have Win7 deployed, but as we haven't yet, we can still make the registry changes before we take an image, and then that will be applied to all users.

Here's a link to remove the 'Libraries' link from the Nav Pane in Explorer.... Libraries Folder - Add or Remove from Navigation Pane - Windows 7 Forums

Well, there goes that idea. I know we use the /generalize option, but we have our answer file set up so that it doesn't remove any drivers.

Do you have it set up in your answer file to not strip out the drivers?

Didn't have that problem, but I did run into an endless loop when it was trying to set up the first user log in. Basically, we went back to the drawing board and started from scratch. Took us awhile to get it to where we liked it. We also... Run Command Prompt as an Administrator >cd sysprep >sysprep.exe /generalize /oobe /shutdown /unattend:answerfile.xml

You have to create a whole new answer file using the amd64/wow64 components, instead of the x86 components. We have our answer file set up so that it just asks you to give a PC name during the initial startup, then logs in as a user, runs PowerShell to add it to the domain, and then reboots itself.

I'm not saying skimp on it by buying a no-name PSU, I'm simply saying you could probably get away with a 650W PSU and save yourself some money in the process. I just bought a Corsair 750W and I probably could have got away with a 650W.

If that's all you're putting in your build, then you most likely don't need a 850W PSU. My PC has 4 HDD's and I had a ton of unused cables from my 750W PSU.

I just upgraded my system with a i7-860 and 8GB of RAM. Paired them up with a GTX 260 and the burns. My 860 is slightly OC'd to 3.0GHz, though.

I downloaded and installed last night and I was pleasantly surprised. I like how they brought back remnants of the "File" menu that we were all used to. I also like how Outlook now has Jump Menus in Win7 for things like new mail message/contact...

Sounds like you might be stuck until the next fiscal year rolls around. You said you're the IT guy for your High School, how does the rest of the district do things? Is each building separate? Here, we have an IT staff of 3 and we support the whole district, K-12, and and all of our tech purchases goes through our department.

Here, we create purchase orders, our Business Manager then approves them, and then we fax the PO to the company. I would definitely push for a budget for next fiscal year. We also had the problem here a few years ago, where each department would order their own tech through their budgets, and that got to be an issue, so now all tech is pulled out of each budget and put into ours, and we do all the ordering for the district. Unfortunately, because you came in without a budget, and the state of CA's finances, you might be out of luck for the rest of the year. What was done before you got there?

I think, if I've read correctly, all you need to do is update the group policy schema to the 2008R2 level. You can do this from 2003 DC's and then you can update it locally from your machine with the Windows 7 RSAT.

We've got a few running off 2003R2, and like was mentioned above, you need to turn off bi-directional printing and they lose their IP's every so often. Other than that, they work pretty well.

I think they removed that in Vista. Here, I just defaulted our domain and have it not show the last user logged on... which you can do through GPO, but the exact location escapes me ATM.

A bit wobbly is right. They changed their whole driver installer. It looks like if you have an XP box, you can download the driver and run the installer. Looks like it installs to C:\Program Files\HP. From there, they are under the Digital Imaging folder. If you're still having problems, I can RAR them up and drop them somewhere for you. Any suggestions, as they are ~30MB?

We have a bunch installed on one of our servers that's running 2003. Just use the XP drivers and if they come as a .exe from HP.com, it's usually just a self-extractor. Set to something like C:\HP and pull the driver from there.

I think I saw something on the TechNet forums about this. I think 2008R2's version number is 6.1xxx and the Exchange setup is looking for 6.0xxxx and lower. I think there's an XML file that can be changed to allow the install to work properly.