Tripredacus

A blank MBR makes sense. I do understand the "simple" reasons why you get a flashing cursor. As I explained it to my compatriot, the system sees the HDD (or the volume) but doesn't know what to do with it. Otherwise it would go to the "insert a disk" type message. I'm just curious as to why installing it on IDE mode works fine, but installing it on RAID mode with iaStor.inf wouldn't write the MBR data. Perhaps it is a bug with this version of Windows?

Can you use Chr(34) in the unattend? What about unicode characters? Did you try <CommandLine>cmd /c start /wait '%systemdrive%\TEMP\SystemUpdate.exe -s -a /s /v"/qn"'</CommandLine>

We don't need to close if you post in the wrong place. We just move it to the right place!

You should be able to set permissions recursively, but you have left out some valuable information for us. 1. What folders are you trying to change permissions on? Is it a foreign disk or a network share? 2. What is your version of Windows 7? 3. What kind of network are you on, or are these "users" local users?

Welcome to the MSFN!

My options for boot are WinPE v1.5, 3.0 (x86 and x64) or DOS 7.1 (which has NTFSDOS). However I thought about this for a moment, while I can boot to DOS I won't be able to load a RAID driver to see the volume... I also have the ability to boot to our test server which has a PXELINUX rom if gives any other options. UPDATE: ran a program called MBRFix from the WinPE 2.0 (x86) which fixed it. However the same program (and commands) did not work from the WinPE 1.5 that XPe installs from. It seems to working now.

Here's the situation. We are trying to install POSReady 2009 (for all intents and purposes, this is XP) on a RAID1 on an Intel desktop controller. Setup is normal (either provide iastor driver via click or putting in drivers folder) it detects the HDD, we can format it and install the OS. Checking the OS after setup (in the PE it goes back to command prompt) we can change to C: and see that there are files there. After a restart, it will not boot off the RAID volume, all we get is a flashing cursor. I have also tried using bootsect on the volume after setup. Boot.ini is correct. You can probably ignore the fact that this is POSReady, as I am just looking for other things to try or other possible reasons why this would happen on XP. The RAID driver is in the "image" already and we are not getting a 0x7b... just a flashing cursor. Booting this into our WDS (WinPE 3.0) we can see the volume has an OS on it, however running Diskpart it shows that the volume is active, but it also shows "Boot Disk: NO" Any ideas? PS: no problem on this hardware using IDE mode instead of RAID.

Verify that the time in the BIOS is set correctly. Check the time-zone in Windows.

Can you post either a screenshot of this message or exactly what the text says?

What OS is in the server and what is the method of PXE (WDS or PXELinux) ?

Billy Joel - Honesty

Ah there was one other thing I failed to mention, and that is handling both MSPs (the new and old) and the company itself. I have seen that "worst case scenario" before where the two MSPs refused to work with one another. And that may end up being a problem when you talk to the MSP to get specifics on what they do. They may not want to help in the transition, or may require to be paid extra for that work. I don't know if they need to be onsite. It would be handy if the new company sent someone there to get details on what they have, and how they do business, etc.

Turn hidden files on first to make sure they truly aren't there. There was a recent strain of virus that would set entire folders or volumes to hidden, causing many people to think their data was erased.

All of the MSP changeovers I've had experience with didn't do a straight up "drop" like your post is implying. Any time a new MSP comes in, usually there is a period of time (1-3 weeks) where a transition is done to get one company out and another company in. This way they can learn about the customers environment without jumping right into it. This isn't so much a software question, so I'll put this in GD for now.

Could be related to this: <meta http-equiv="X-UA-Compatible" content="IE=edge" /> I can find mixed results of using the Edge value. Some have problems, some say its made for HTML5. From what I understand, using edge will force IE8 to use the IE8 renderer instead of the IE7 (Compatibility) renderer. Then again, I've also read that IE8 may totally ignore this value, so not sure if it is related.

Some programs, even if running in the background, can keep the screensaver from coming. Do you have a screensaver set to a time less than the sleep of the monitors?

When you say Windows Update, do you mean the website is in English? Also, if this notebook connected to the internet via a Swedish ISP?

You can also make a recovery partition with Ghost and Acronis.

If it is 0x3b, it is likely due to memory corruption of some sort. But that isn't much info you provided. There should be other Events listed under Application or System with more info. Is this BSOD reproduceable?

This seems less a Windows 7 issue and more of a network/server issue, since it is confirmed that allowing microsoft.com to not be authenticated will fix the problem, but your IT won't allow that. Have you tried allowing WDS to prestage all systems into a specific OU, then you can allow that group to access microsoft.com without authentication. Or even have these systems use a specific user account that has access through the proxy.

OK let me understand this. You are (basically) using your deployment server to be the proxy between the clients and the MS Activation Server? When you say you disable the firewall and it works, disable it on where, the client or the server?

The ports that Activation uses should already be allowed by the built-in firewall... as it uses IE to do the activation. http://support.microsoft.com/kb/291983

Did you already see this kb? http://support.microsoft.com/kb/921471

Not so far that we can tell, however the site that had done the (Ultimate) DVD install is notorious for not relaying problems back to us... I know they did not use the WDS to image it because I haven't put the NIC drivers in the boot.wim yet. We have another one coming in I can test again. I'll at least try deploying another (different) image to it.

How is your notebook set up to use this monitor? By saying that both are on, you can either be using an extended or cloned display. My notebook will turn its screen off as soon as I connect an external monitor to it, so the behaviour is different than in your case.