Tripredacus

OS: Windows 2003 Standard SP2 Event Source: WDSServer Event ID: 769 http://technet2.microsoft.com/windowsserve...3.mspx?mfr=true This is a network availability "error" where at any point in time that the server attempts to make its connection active, it has a problem. Sometimes I get a lot of these errors, sometimes I get none or barely any. You can get this error if you have too many connections made to the Server, but it shouldn't be that it is possible to get this error with nothing running on the network! Which is how it is for me right now. I've got the Domain Controller (WDSS) and the DHCP Server running right now, nothing else, and still getting these errors. Any ideas?

I've done this previously and it always works, but today none of my peimg commands are working. First I exported an image to a new filename because I needed to add drivers into it and I didn't want to break the original. Then I mounted it to c:\winpe_x86\mount. I used PEIMG as I normally would to install drivers, but this time it gave me an error: Thinking that perhaps the image was wrong, I mounted a different WIM (that I hadn't exported) and tried to inject those drivers but it failed with the same error. So I thought the drivers were bad and tried to inject known good drivers... That also failed. I unmounted my image and checked the info on both the exported image and the other one and it all came back OK. I can't figure out why PEIMG doesn't like putting the drivers into the mounted volume today... Here is a cmd example: peimg /inf:e:\drivers\targus\cmdv\*.inf c:\winpe_x86\mount\windows I have also tried specifying the INF name, using an equals (=) instead of a colon ( and it just isn't working anymore. I also rebooted the computer but that didn't seem to make a difference.

Haha that might have something to do with the lawsuits!

You should probably turn DCOM back on. A lot of programs require that to be running.

AutoIT is an open source scripting language used to write programs. I can only surmise that the program you are trying to run is written with an older or non-beta version of AutoIT, or is not meant to be run in Vista.

I have to say that one of the hardest parts of this project is that upper management thinks that we (the guy who handles the REAL server and myself, who handles the product testing/development) can get the new server system up in running in no time. He has no idea that we will have to do tons of testing first... uggg... Today I actually did some more work. On the 2003, I added the new server (GEARS) to the Domain Controllers group, and added a domain user (SHARK\GEARS) to the Domain Admin group. Then I joined Gears to the Shark domain, and added the roles of AD DS and WDS. I also added some functions such as Backup Services. To my disappointment, I was unable to add Hyper-V because it said the CPU was not supported, even tho the server has the 2 dual core Xeons in it... What exactly does Hyper-V require anyways? I also formatted the RAID-5 and was pleased to see the 1493GB listing there in Disk Administrator! I still have a bunch of notebooks to image using the 2003 as the WDS, so my role migration will have to wait until those are done... I do have a question regarding my config with the 2003 server (UNCLESOCKS)... here is the setup: Domain Controllers: GEARS (Computer) Delegated Control for active directory functions to GEARS (Computer) Domain Admins: GEARS (User) but when I log into GEARS, I use the Administrator account. Should I add GEARS\Administrators into the Domain Admins group instead? When I log into GEARS, it doesn't give me an option to log into a domain, or is there another option I should be enabling?

Well I got it installed by using the admin switch with msiexec, but it still won't open because iTunes itself checks for the service pack. I did attempt to change the registry so it registered as SP2, but iTunes doesn't check the registry for SP information, it checks winlogon.exe. I reshacked winlogon.exe to change the version info, but I know full well I can't replace it while Windows is running. It also appears that I can't get into the BIOS on this computer because the system registers a USB keyboard AFTER it accepts keys for BIOS entry. So the idea of booting off a USB Key and using NTFSDOS to back up and replace the winlogon.exe idea went out the window. Maybe if non-Apple software won't cut it, I'll dig up a PS2 keyboard to get into the BIOS to change my boot order. A curiosity, even tho I changed the information for version, CSDVersion, etc in Windows NT\CCS, after the reboot the new values I added disappeared automagically.

Updating is not an option. And my computer isn't vulnerable just because its using RTM. It has been modified to have various features of SP1 and SP2 without installing the actual service packs. And besides, Windows Update does not work because my XP is VL and it checks if the PC is on the domain (which it isn't anymore) and if it isn't, then Windows Update rejects my COA, even though it is legit. Basically I need info on what MSIEXEC checks when it looks to see if the update is installed. I do not use all the extra features in iTunes, I only use its ability to copy files to the player. If it becomes too much of an issue, I may have to look into alternate software for the iPod but i'd really not like to deviate from using the Apple software.

Dummy me never thought of that! in other news: I figured out the differences on my own but perhaps this post will be useful to someone else.

While the two boards I listed use the Intel 1000, they actually use the 6032 inf and not the 5132 inf.... I took me a few hours to figure out. :\

It seems like you seek information on GhostExplorer? I can't think of how you have changed the GimageX... if you could put paint in your WIM, I wonder if it will let you take a screenshot and save it to a USB drive?

but when the system startes I had to enter the username and the product key manually desopite that I had created the autounattend.xml file in the sysprep folder Check this site out: http://www.svrops.com/svrops/articles/sysprepvista.htm#xml1 Maybe that will help you?

It's in BIOS, nothing much you can do about it, unless you want to start fiddling with BIOS, NOT, and I mean NOT recommended, you could end up with an unbootable system and need even a replacement BIOS ! jaclaz No this information is stored in the Master Boot Record, not the BIOS. I am in process of duplicating this issue as well, but I can't really tell you much about it because of IP reasons. However volume imaging solutions (such as Ghost and Acronis) save the MBR in the image, but Imagex being file based does not. Anyways, this is also part of the reason why the OPK documentation (as well as WAIK) say that "recovery" aka EFI partitions must be the first partition on the drive. Dell, however, doesn't use WinRE for it's recovery partition, which is why it isn't Part 1 on the drive... Dell doesn't use winRE?! what is it then? winPE? Dell uses another company's product to create their recovery partition. This company creates custom recovery options to make it look natural to the OEM that sells/distributes the computer. Because my company and the recovery provider are clients, I cannot divulge additional information, sorry. A WIM installation, at its simplest, is a partition you can boot to that may have a simple interface, that basically applies the WIM to your C drive. Which is basically what the Dell Recovery partition does but it asks you stuff to make sure you want to do it, etc.

Try mounting the WIM with the PE Tools Command Prompt, then look for the XML file. It must be in there someplace. I haven't tried it myself, but then again I don't seem to be using the deployment method you are.

Again, if you are keeping the same functional domain level, there's nothing to change. Add the 2008, remove the 2003. The network should not be affected. If you intend to move to a native Server 2008-level domain, then you would need to make a brand new domain. Should you decide to make a brand new Server 2008-level domain then you will have issues getting Server 2003 boxes to do stuff in that domain. Ideally a Server 2008 domain is ALL Server 2008(+) DCs. There are some little things about 2008-level domains (and forests) that make them appealing, but for smaller setups those things aren't very important. There's some network optimizations for the databases and stuff but overall a 2003-level domain is fine for small and even medium-sized domains still. The idea ATM is to not remove the 2003. I currently use 2 2003s for the setup, the idea is to run 2008 as the main AD DC and the 2003 as a backup and run DHCP only. Removing the 2003 is not a priority right now. The other (the one with the busted RAID) I wish to remove from all domain activities because its failing as it is. If that server weren't so *blasted* important it would have been in the dumpster over a year ago. Eventually, the setup will be two 2008 x64 servers but for now I want to learn partial migration for them. Aside from my own learning, it may be useful information for our clients. EDIT: sorry didn't know about the swear filter lol.

This isn't always an option. Some manufacturers only provide BIOS update utilities that can be run from Windows, such as AOpen. However the general rule is if you download an update utility that is 16-bit or says for you to boot off a disk and run it, then yes, don't run it in Windows. And your OEM (HP) has a Vista BIOS listed because it supports the OA2 containing their OEM information. If you were to, for example, put a new BIOS for the board that wasn't from HP's site, then when you logged into Windows, it would ask you to activate. But if you are installing a fresh copy of XP and using your own Product Key, you'll end up activating anyways so the newest BIOS really isn't required. I recommend look at what the update does compared to the version you have installed and see if it makes sense to you to upgrade.

Or you could just delete the connection in Network Connections...

If your XP CD is Service Pack 2, it will automatically detect whether you are using a single or multi-core processor.

iTunes 1.6 won't install because it errors out saying it requires Service Pack 2 or higher. Is there a way or a switch to install this on a non-service packed XP? Or what does an MSI check in the registry when it looks for the service pack? Can I spoof it so it will install anyways? Today iTunes greeted me with a message saying my iPod was unusable unless I upgraded to iTunes v7.6. I went to apple.com to download the new version and it greeted me with this message: Any help?

Update! On Friday, I got fed up with the DHCP server and the fact that the mouse wasn't working... So I decided to reboot it. Well on the way back up, another drive fell off the array and the two remaining showed up as DEGRADED. I didn't want to deal with it then so I shut off the monitor and left for the weekend. Today I came back in and somehow the server recovered and I logged into Windows. It still didn't recover the 4th drive but it must have rebooted over the long weekend and found the 3rd drive that fell off on Friday. I am lucky for that because I was still able to use WDS and an RMA came in and that server was the only place that had the image I needed. Today, the new server was set up with 2x 80GB mirror for the OS drive. Server 2008 Standard x64 was installed and it took about an hour. Then the 6 drive, 1.45TB RAID-5 was built. Those few steps took about 4 hours, and now the server is waiting for me to set it up. I haven't came up with an idea for a domain or computer name yet. I do have some questions regarding the migration I need to do. Here is the situation: I have my 2003 Server (computer named UNCLESOCKS) that is a domain controller and the domain is called SHARK. Now I am pretty sure the new domain won't be SHARK but I might keep it if it is easier. What I need to do is take the new server and make it the top-level domain controller, and then take UNCLESOCKS and set it up to be the backup domain controller. So here are my questions... 1. Is there a tutorial on how to switch a server role from the primary to backup domain controller? 2. Is it important for me to unpromote UNCLESOCKS before I promote the new server? 3. Would it be easier to use the domain SHARK rather than starting fresh? 4. Is a 2003 Server capable of being a backup domain controller to a 2008 Server? 5. Does Windows 2003 have the ability to automatically backup files from another computer, using a differential or incremental synchronisation? 6. If yes for #5 (or with a 3rd party product) Would there be a problem if the 2003 Server backed up data from the 2008 server? As far as the AD portion is concerned, I have not created any additional OUs and only 2 user accounts on the SHARK domain, so I would not need to worry about AD migration from one server to the next. I will also like to find information regarding the virtual desktop/terminal emulation using virtual OSes within 2008 that our Microsoft rep told us about.

I think the problem is that "Setup/Uninstall" shows up as a program to execute files.

1. Post your notebook model number. 2. Go into the BIOS and try setting the Drive Configuration to IDE instead of AHCI, if it has this option that is. Some notebooks come with AHCI as the default controller type and without the driver disk, XP won't see the HDD. However if you change it to IDE, you won't be able to switch it to AHCI later. I am not familiar with the differences in those controller methods so I can't tell you that.

The sysprep folder will become delete after the user goes through the sysprep process. If you bypass the system setup, by unsealing, the folder will remain. When you go through the welcome screen and fill out all that information (depending on your unattend) you notice that the computer reboots before going into the desktop. The sysprep folder is deleted at this point and why it does just go into the desktop after the welcome... since it wouldn't be able to delete itself. Are you encountering problems during the autounattend portion?

It's in BIOS, nothing much you can do about it, unless you want to start fiddling with BIOS, NOT, and I mean NOT recommended, you could end up with an unbootable system and need even a replacement BIOS ! jaclaz No this information is stored in the Master Boot Record, not the BIOS. I am in process of duplicating this issue as well, but I can't really tell you much about it because of IP reasons. However volume imaging solutions (such as Ghost and Acronis) save the MBR in the image, but Imagex being file based does not. Anyways, this is also part of the reason why the OPK documentation (as well as WAIK) say that "recovery" aka EFI partitions must be the first partition on the drive. Dell, however, doesn't use WinRE for it's recovery partition, which is why it isn't Part 1 on the drive...

I am not sure if Intel pulled a stealth revision or what (they've done it before) , but we have two motherboards that do not work with both the WinPE 1.5 and 2.0. They are the DG33BU/FB and DQ35JOE. They both use the Intel PRO 1000 NIC (DEV_10BD) and they BOTH used to work with the PE versions we use here. I have installed the most updated driver for this device and WinPE 2.0 still does not see the network adapter after I initialize the network. Any ideas or any problems with this controller recently? EDIT: please move this topic to the Device Drivers forum.