Tripredacus

WDS allows you to have multiple boot images. I know it can do both 64 and 32bit (if you have a 64bit server OS), but I haven't tried a 16bit boot image. WDS can also have Linux boot images as well. WinPE (what I use so far) v2.1 comes in 32 and 64bit. There is an older version, v1.5 which was the Server 2003/XP PE (available to OEMs only) and also is what things like BartPE uses. But honestly, if you are going to do this for imaging, you should check out Imagex. Its a file-based imaging solution as compared to Ghost, with is Volume based. One downfall is that Imagex won't capture the boot sector and/or MBR like Ghost does, and it only understands NTFS and FAT/32. Basically, you will find a lot of different answers to this kind of question, because there are lots of different ways to do it. And we all do things a little differently than everyone else.

One advantage of using a PXE server is that you can keep all your software in one location. You also wouldn't need to manage or carry around a bunch of media from machine to machine. Let's say you use CDs or UFDs to have your software on it. What if you need to make a revision, upgrade the software or change anything? You'd have to make all new media again. And you also run the risk of having outdated copies still being used if you aren't the only one doing it. Also, what do you do for computers without CD drives or have CD drives but you need a DVD drive? Basically, you need to figure out what your computers can handle. If 95% or higher can support PXE, then this should be your goal. I still have CDs and UFDs around to handle those older/oddball computers that can't boot to the server, or don't have enough RAM for the Ramdisk I use, etc. But these types of machines are in the minority for me. Also, you may want to start off using media for now, but eventually migrate to using a centralized method. This would be a good method if you are having trouble understanding PXE, or more likely, getting it to work.

Sometime next week I am going to install Windows 98 on an MSI Wind netbook to see how it works out. Are there any recommendations or things I need to know about installing 98 on newer hardware? I haven't installed 98 on anything newer than from 2001. Also I know this has been questioned before but don't remember where the thread was. The Wind config can be found in the "My Servers" link in my sig if you need that info. Thanks.

I haven't encountered a problem like this with any of my x64 installs. I have done both official (hard copy) beta and later releases without a problem. It likely doesn't care about the optical drive itself but the mass storage controller. Are you using an ATAPI or SATA DVD drive?

Dean Martin - Volaré

What makes you think so? Retards are everywhere on this planet. It might as well be a banned user that's frustrated or something. Maybe I'm stereotyping, but I have found that alot of intrusion attempts on my network is from Asia, China specifically. And there's quite a bit from South Korea. I would have to say about 50% to 20%. The rest is from other places like Russia, Brazil, East Europe, even Africa. I guess that's how being cynical warps your thinking. If it were totally random, we'd probably jump to that conclusion also. It originally started with a member(s) that once belonged here, so that's one way we know where its coming from.

What happens if you apply the image using Imagex?

I have a hunch that this isn't going to be strictly PE related. Validate your answer file in WSIM and see if it comes up clean. Otherwise, when you post your answer file (unless you correct the problem) then I will move this thread to XP Unattend forum.

I am starting a new Vista Unattend and I got an error during WDS Deployment: I checked Panther and it basically said it couldn't find the hard drive. And indeed, the hard drive was blank. So I decided to check my XML in WSIM, and I needed to generate a new Catalog. WSIM gave me an error: It led me to a log file, and I'm not really sure what to make of this. Any ideas on what direction I should be going in? 1:56 PM : 1:56 PM : Windows SIM was unable to generate a catalog. For troubleshooting assistance, see the topic: 'Windows System Image Manager Technical Reference' in the Windows OPK or Windows AIK User's Guide. 1:56 PM : 1:56 PM : System.ComponentModel.Win32Exception: The specified image file did not contain a resource section Server stack trace: at Microsoft.ComponentStudio.ComponentPlatformInterface.WimImageInfo.PreCreateCatalog() at Microsoft.ComponentStudio.ComponentPlatformInterface.OfflineImageInfo.CreateCatalog() at Microsoft.ComponentStudio.ComponentPlatformInterface.CatalogCreatorImpl.CreateCatalog(OfflineImageInfo offlineImageInfo) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Microsoft.ComponentStudio.ComponentPlatformInterface.ICatalogCreator.CreateCatalog(OfflineImageInfo offlineImageInfo) at Microsoft.ComponentStudio.CatalogGenerator.CreateCat(ProgressDialog pd, Object o) Update The error above was using the Install.wim from the Vista DVD. So I thought maybe there was a problem using that. I exported Image index 1 (Vista Business) from the Install.wim and added that instead. This is how I did it in 2003 anyways. But it still makes this error. However, WSIM is acting up also. It gave me an XML (node is missing) error opening it once, and sometimes it won't close and I have to use Task Manager. Thinking perhaps there is a permissions issue, I have done the following: - added the logged on user (is already Builtin/Administrator) to the Enterprise Admin group. Also changed local security policy to always elevate (which removed UAC prompts). Environment is Server 2008 Standard x64 and OPK Tools (think WAIK) for Windows 7 RC.

The link you posted does not work.

I need some information from you. 1. How do you connect to your modem, with LAN or Wireless? 2. What is the make and model of your modem?

I believe SP2 and SP3 keys are different, or am I reading your post wrong?

Try the following: sel vol c detail disk detail vol detail part You can also try list vol list disk

I've heard so many things that Spybot does to Windows, add this to the list. Winsock can get corrupted very easily, although I do not know how to stop that from happening. You'd think that Winsock components would be protected system files but I guess not.

Not to confuse you further, but not only can Altiris launch Ghost or Imagex, you can also launch Ghost from Rdeploy!

Just got this idea. Use for you dedicated 9x guys.

So right now you need to run a compatibility check. Make sure the architecture version matches between the app and the PE. Also run it on Depends (Dependency Walker) and Process Monitor to see if you are missing any files. If this program requires .NET Framework files, you might be out of luck.

Yes, at the time I wrote this guide, I was converting an existing Ghostcast server to WDS. You can use an existing DHCP server, or you can use one computer for everything. I just transferred most of the roles off the server I had used, so I can't really tell you the settings needed for that.

How do I update this Windows AIK to RTM version? THANKS BYE When the final version comes out. You uninstall the old one and install the new one.

I don't believe that you can.

Can you post a screenshot?

If you have a Service Agreement with Altiris (Symantec) this question might be better suited for them. The Altiris suite is a high end and expensive product and you may find that most users here may not be in the large corporate environment that can use it. When I used Altiris 6, it launched Ghost. I do not know if Rdeploy has the ability for you to inject drivers into it, or what that process is. I can make this workaround recommendation. 1. Deploy the image onto a known working machine. Use this as your test machine. 2. After it is deployed, do not boot or reboot. 3. Capture the image with Imagex. 4. Inject the drivers into the WIM file. 5. Reimage the computer with Imagex and your modified WIM file. Again do not boot or reboot after imaging. 6. Recapture the image on the computer with Rdeploy. You should back up your existing Rdeploy image in case this does not work, so you can restore it easily. Now this means you will have a fully editable version of the image as a WIM, as well as your Rdeploy copy.

Welcome to the MSFN!

Now newer anymore! See this one: http://www.msfn.org/board/index.php?showtopic=136269 Welcome to the fold. Make sure to check the Forum Rules, we have a part about the signature.

Wow already a sponsor! Good job!