Tripredacus

Was it re-authorize the DHCP server to refresh the records on it Well I am thinking that it is getting this error because DHCP on UNCLESOCKS is disabled, and I am authorizing the legacy to run DHCP instead. I did it this way because I couldn't get any computers to boot via PXE with DHCP and WDS running on the same computer.

Indeed this is enabled. What is that service used for specifically? When I installed DNS, it turned that on as well, or perhaps it was already running before the machine was given to me for testing...

Hey check your power supply!

Partition Magic has the ability to create a bootable CD or floppy disk set. That way you can boot into Partition Magic and it doesn't have to be on the Hard Drive.

Here's an update, as I have fixed my problem with a work-around. I contacted Apple Support and they recommended connecting it to a Mac to downgrade the firmware. They said that this would allow it to work with previous versions again. I called up my cousin because she had a Mac, and to get it taken care of. It turned out she also had the older iTunes installed, and when she tried to update it, she was told her MacOS was out of date. So that idea went out of the window. She recommended I take it to the Apple Store and have them downgrade it. Well, the guy (Mac Genius) at the Apple Store evidently are not of the same mental capacity as Apple Tech Support. They reset it for me, but said that it would still only work in an iTunes 7.6 software, because the firmware does not dictate the software version required, but the "software" that is installed on the iPod itself. I was pretty bummed at this point. So I downloaded the SP2 redist, and was about to install it when... I just wanted to try spoofing the service pack again. So I connected up the iPod when suddenly... WINAMP DETECTED IT! Here's how that happened. A couple days before, I tried out the new Winamp version. I did not like it because it was really slow compared to the older version when it came to ffwding within tracks, and there was a pause when crossfade was enabled. So I had uninstalled it and reinstalled the older version. Well even though the older version did not have iPod support, the uninstall for the new version must not have removed all of the components. So the old Winamp detected the iPod plug-in, and thus the iPod. It was also able to erase and copy songs to it. My last step was to uninstall the iPod updater, iTunes and the Apple Updater. The best part is that Winamp can also copy album art to the iPod as well, and the sync time seems to be faster. So once again I've managed to NOT have to install any service packs to get something to work.

It is formatted FAT32, and appears as a EISA partition in Disk Administrator, without a drive letter. I also tried the other application on that site, MBRWORK, which appeared (at first) to be a hopeful fix. My test computer (where I am doing the MBR work) is a clone of computers that we currently image daily. So I have ready access to production units. I captured the MBR off one of the working production units, and then applied it to my test computer. It went through without error, and displays the appropriate information on the screen during boot-up. However, it did not respond to the "R" key and the "F10" key did not seem to work any better than before.

This program did indeed give the ability to get a keystroke from the user while displaying information on the screen. However it would not boot the recovery partition I use. It is a hidden, no drive letter 0x12 partition that IS bootable. Except when I press F10 (instead of F12) it tried to boot off the network. I disabled network boot in the BIOS and it will then say "No Bootable Device"... So it seems that the MBR.EXE is looking for a different type of hidden partition than the one I am using.

http://www.microsoft.com/windowsserver2008...icalInformationYou need Xeons running Intel's VT from this list (Select "Intel Virtualization Technology" from the "Supported Features" list and click the "Filter on Selections" button). I am not sure if it's a guarantee that everything on that list will work, but it's for sure anything not on that list isn't . Perhaps there is something I need to enable in the BIOS, or install from Intel's website so Windows sees that it is capable of running it. We are going to need to use Hyper-V to support our legacy customers (ie those who require 16bit Ghost to be used). This would be an excellant time to look into Microsoft Deployment ToolKit. Using this and the MultiCast Feature in 2008 you could image all your laptops in a relatively short time I am already using that, but we can only use the deployment features provided by the OPK toolkit, not the "corporate" toolkit. Right now, these notebooks can image in 3 minutes using the 2003 WDS. So with this relatively short image time, it is not a problem to do one at a time, since we don't get that many orders for that notebook model at once. But, using WDS on the 2003 for production is not the original idea, its just that some network controllers (software controlled like Broadcom57 and Realtek 8111B) do not work with our current imaging system. In other news, the 2003 server started acting up ever since I joined GEARS to the domain. It now sees our legacy server as being a 'rogue' DHCP server, even tho it is available as a managed DHCP Server in UNCLESOCKS' DHCP management control panel.

Simple File Sharing does not change how security works in Windows, it just changes how you can see and interact with it and its settings.

I have similar experiences with our corporate Anti-virus. It likes to detect my programming tools as 'trojans' and 'hack tools' and tries to erase them from my hard drive and our network drives. In my case, there doesn't seem to be an option to make it ignore those things...

Im not sure about converting a Vista, but it should work if you create a generalized sysprep image of it, then inject the driver? But is there a specific reason you want to use AHCI instead of IDE?

I am not sure if Ghost can manually do this for you, but to make a bootable CD/DVD (I used a DVD) you make it similar to a floppy boot disk. And make an ISO using oscdimg and use the -m command, and also use the appropriate bootloader. Or just make a WinPE CD and put Ghost32 on it, and the image. I don't see why a floppy is required.

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.