IcemanND

Sounds like you have the exceptions for file and print sharing set to allow only from it's own subnet. Go into the control panle go to administrative tools open windows firewal with advanced security, find File and print sharing..... in the list there are abouot 8 different ones so you can get very granular, select the ones you need change and open them go to the scope tab and change the settings to your needs. This used to be much easier in xp, but you didn't have the granularity.

And that's a load of manure. I've been using images for 10 years and imaged 5000 to 10000 machines a year, the only issues I've ever run into are with applications that tie themselves to the hardware, thank you AutoCad, and trying to make them go across HAL's, which I don't do unless it is specifically supported by Microsoft. I've also done 3000-4000 scripted installs a year over that same time frame it all depended upon the breed of Windows XP/200/95/98/ME whether we owned the machine or someone else did. But it's really 6 of one and half a dozen of the other. Also depends upon how you handle the rest of your environment. Let's see the normal arguments: "But it's stale the moment you capture it." so is your scripted install, once updates are released you have to update your process just like I update mine. "Mine works across all hardware" Big wup, when was the last time I had to drop an image on a Standard HAL machine.........can't remember. With a 3-4 year swap out schedule here all of our machine fall into the ACPI Uni/Multi category. After that it adding drivers, hmm, you have to do that with new models also. Oh you just drop them into a folder, so do I, ghost images have been editable for awhile now, but I do it when I install the updates. "Scripted installs are faster" ???????? My image installs 6 minutes from boot to usable machine. "Imaged machines run slower." never seen a difference, except when someone tries to force a HAL in where it doesn't belong. I'm sure I missed something.

first try: 35 secs

Thanks for the info. I was afraid that this was going to be the answer. Now the fun part breaking the news to the customer.

Short background: Company has hired me as a contractor to get their systems set up. They already have and have been running on a SBS 2003 server for the last few years. They recently, before hiring me, bought a second with the hope of setting it up in some form or redundancy. I've found that SBS2003 does not support clustering, I can apparently setup the new server as a backup domain controller, but that still leaves the Exchange server and file server, DNS etc. I'd rather not do backup and restores from one to the other, it would be much nicer to have one mirrored to the other but I'm not finding a solution in that manner. Any suggestions out there?

just change to the drive letter. If you are not sure what it is you can type: echo list volume|diskpart And it will list all the assigned drive letters: Microsoft DiskPart version 5.1.3565 Copyright (C) 1999-2003 Microsoft Corporation. On computer: LAPTOP1-XP DISKPART> Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 D THE_ART_OF_ UDF DVD-ROM 1695 MB Volume 1 C main NTFS Partition 149 GB Healthy System Volume 2 F NTFS Removeable 7680 MB DISKPART>

I've only had issues accessing encrypted drives when booted from a WinPE 2 cd. If it is booting from your cd/dvd there should be a drive letter for the CD/DVD. Check out my guide here: http://www.msfn.org/board/index.php?showtopic=101383 driver installation is on page 8.

You can put your image at the root of the DVD that way it doesn't load to memory. As far as reading external or internal drives, if it is not reading the USB drive try adding the chipset drivers to the image or you can load them after booting to test. For internal drives try adding the SATA controller drivers.

What are they going to do (doing) with vista? It's default install is IMAGE based? What's this other guy going to do reverse engineer Microsoft and go back to the XP way of installing?

do a repair install of windows 7

With previous versions of windows you had to install the newest last to have the multi-os boot options work right. You should be able to do a repair install of Windows 7, or it will likely just do a repair of the startup sequence to fix the problem

Having spent the day looking around and finding nothing but other people searching for this answer I gave up and dug in to find out what I needed to do it. Here it is, at least what I have found so far. Copy cdosys.dll & msoert2.dll from a Vista machine to your boot.wim file. Add the following command to startnet.cmd: regsvr32 -s cdosys.dll That's it. Run your scripts and send your mail. I've not attempted attaching a file yet, but all of the other standard functions of CDO.Message have worked so far.

So you've booted from CD, cmd prompt comes up x:\windows\system32> You enter: imagex\imagex.exe /apply 1 sony.wim e: You get back an error that "the system cannot find the file specified" Where do the imagex directory and the WIM file reside?

what error or problem are you seeing?

Let's see, make a CMD scripted style menu that lovely dos look, use VBS/HTA, or an Autoit script would also work nicely for this, how pretty do you want it to look?

http://www.backsettings.com/outlook-backup.html

FROM does not follow the rules, see post 1. Back to VAGA

MOVED Why not just set the Exchange account up again as a secondary account in outlook? Then it will redownload the cache from the server and you can copy it manually to a local PST.

There is no Warez section here. and no further discussion of it. Any further discussion will result in banning. CLOSED.

Think that's bad I know of professors who still use qbasic as part of their courses.

What version of ghost?

NUTTER, Take the rest of the day off. The internet has told you to. 75%

search for offline sysprep

Well saying it is a schooll porject kind of shot yourself in to foot. But adding a SATA drivers to a Sysprep image is the same as adding a ATA driver that is not already included in an XP install.

This isn't a registry tweak it is set via Boot.ini options