ButlerKevinD

Well, I would tell you how to check it, but it would probably get me banned. Check with your schools IT Dept or whoever it is that is offering the cd/iso download. Most schools with large Micro$oft deployments usually qualify for their VLM key, which does not require activation (mostly for the desktop os and Office). But since you are a student there, they probably won't let you all run off with a VLM key (I know we don't). What are the requirements and restrictions on getting the copy from your university?? With our faculty and staff, if they ever leave, they must remove all installations of university licensed software.

your boot.ini looks correct. i cant imagine what could be screwing up. i have an ibm thinkpad that i dual boot between the english and german versions of windows. here is what mine looks like: [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional English" /noexecute=optin /fastdetect multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional Deutsch" /noexecute=optin /fastdetect the only differences, besides mine being 2 32-bit installations, is the cmdcons line at the end of yours. i see that you have these installed on 2 physical hard disks, where with my install, i have 1 disk with 2 partitions. have you tried changing the value of "default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS" to "default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS" and see what happens there?? does it default to loading xp x64?? if you do manually edit the boot.ini, make certain its flagged with the system and hidden attributes.

Thats what bootcfg does for you. When I manually edit boot.ini I almost always screw it up. <{POST_SNAPBACK}> can you post me a copy of yer boot.ini so i can see how its configured??

What does your boot.ini file in the root of the c:\ partition look like?? Generally, you should be able to modify it. Just make certain you have a backup in case you make an incorrect change to the file.

I believe unless you're an OEM or VLM customer, no PE for you. What all are you trying to config for the unattended install of XP x64? I'd be interested in seeing what you have tried thus far.

Where does keeping an open mind offer justification for throwing the EULA out the window. You are not happy with the current limitations of your copy of XP x64. There is a huge difference between slip-streaming your OS and hacking a file that limits your use of a PID. A competent attorney would tear your "open mind " defense to shreds in open court. <{POST_SNAPBACK}> Ok, so tell me the difference between either having the actual original cd's of the retail, vlm, and oem cd's, downloading with an MSDN subscription those same cd's, or doing what I suggest when the only difference in all cases is the pid # on the cd's themselves?? This is of course taking into account that you do have legitimate product keys to install them with. And I apologize for assuming that you and everyone else that has posted on this thread is not openminded, but one tends to take offense when the first reply they read hints that they're looking to get the software for free.

Yea, you're probably right. Oh well, it was a fun ride while it lasted.

So, wouldn't this also apply to creating the slipstreamed cd's that just about everyone here has made at some point in time. After all, that could be considered as "reverse engineering" to some. If this were the case, I guess we couldn't talk about and discuss anything in the forums here, now could we. Editing the setupp.ini file as I stated before is no more different than one of us placing a winnt.sif file into I386 with all of its customized settings. You still need to have your product key that accompanies your copy of XP (be it retail, oem, or vlm in nature). Technically, changing the uxtheme.dll would be considered reverse engineering, as you are modifying it to do something that it is capable of doing, but does not by default of the way it was originally released. And how many forum posts are there that discuss this?? I've lost count myself. But to put this to an end, it turns out that modifying the setupp.ini in XP x64 does not work akin to 2k and xp. So, I guess I will have to wait until our VLM iso AND product key are available from our MSDN subscription. Thanks alot for the lack of keeping an open mind in regards to my question. Guess next time I'll make sure to ask one that is more on your level of comprehension. <{POST_SNAPBACK}>

I really dont see how changing the pid constitutes a breach of the EULA. If there is definitive verbage to changing it, shoot me a link or something. If one has an MSDN subscription (which we do), and are able to download via said subscription all os flavors privy to that description, whats the difference in downloading 2k, 2k3, or xp retail, vlm, or oem images when the only thing that seperates the different versions happens to be the pid id in the setupp.ini. To me, thats almost like saying you cant modify the unattend/winnt.sif file even if you own licences for that version of OS you are installing. You will still need to have a (legit) product key to install them with. I am well aware of the need and legality of the product key, so that is a moot issue to me. The key we have allows 10 installations, so its just a matter of time if and when Micro$oft starts offering VLM keys. And since we do have VLM's for all of our x32 installations of 2k and XP, it would only make sense to do the same for XP x64. Of course, this is my opinion on the matter. Everyone that has replied here seems to be way too much on the legitimate bandwagon, and the assumption that I am looking for this info for nefarious intentions, which I understand the reasons why completely. But lets try to quit thinking and acting like Micro$oft for just one second and thing outside the box. If this were the status quo for everyones though processes, then I'd imagine that Bart Lagerweij would have just said to hell with BartPE without even looking into trying it out first.

READ THE ORIGINAL POST!!! I mentioned nothing about changing the key. The key we have is from a Microsoft rep that we go through at my place of employment. The only thing I mentioned was modifying the setupp.ini file in \i386. Changing the last 3 digits allows the following: ExtraData=707A667567736F696F697911AE7E05 Pid=xxxxxxxx xxxxx270 - Corporate/VLM xxxxxoem - figure it out xxxxx335 - retail You can check out http://www.webtree.ca/newlife/windows_xp_tips.htm and look at the first post on the page. It spells it out clear as day. I know Micro$oft has a knack for changing things around, so this is why I am asking. It's really not that hard a question. I realize that you seem to have major wood for busting the little newbies and script kiddies that want to brag about the warezed versions of server2k3sp1 x32 and x64 and winxpx64 that are out there in the newsgroups, but I'm just looking for a simple answer from the community at large their thoughts on this. And yes, I have tested the key from the .nfo files out in the usenet, and it does come back as a retail key, 30 day activation. Big supprise. Changing the Pid from what I have found on XP x32 is no more different than having an OEM, VLM, and Retail copy of the os in front of you. You just have to have the corresponding key variants to install them. The same Pid scheme holds true for 2k, only with the corp/vlm config, it does not even ask for a key. So, once again, any thoughts on this, or should we just close this thread all together????

Haha... real funny. You know, some people do actually get legit software from other sources than newsgroups and irc. But thanks showing me that your comprehension of the English language is a bit lacking. So, anyone else care to take a shot at my question??

Has anyone tried reconfiguring the setupp.ini in \I386 of XP64 to change from retail-corp-oem. I know under the 32-bit flavor, changing the last three digits on the second line of the file to 270 will allow it to accept VLM keys, wasn't sure if the 64-bit flavor followed the same guidelines. Any thoughts on this?? And before anyone hints to it, I'm not trying to score a key. I already have my legit retail one. Just doing some legwork before I ask the boss to get us a 64-bit VLM key. Thanks in advance.

Sorry for the dupe?? So, where is the answer Mon Ami!!

Hey guys, he is the op... I just got volunteered to create a cd that has XPSP2 upgrade on it, and will install with the user merely inserting the cd and the autorun kicks in. SO, I have d/led the full XPSP2 from M$ and created an autorun.inf file and placed it in the root of the cd along with the XPSP2 file. here is my orginal autorun: [Autorun] OPEN=xpsp2.exe /passive /forcerestart /n /f [Autorun.x86] OPEN=xpsp2.exe /passive /forcerestart /n /f This works like a champ. Does not have any problems installing the service pack, reboots the system, and only displays the progress bar. Now for the problem. I was informed that some of our workstations that are limited on hdd space, this config will blow up due to it actually extracting the service pack onto the hdd. So, I tried extracting the sp to a seperate folder and creating the following autorun.inf: [Autorun] OPEN=update\update.exe /passive /n /f /forcerestart [Autorun.x86] OPEN=update\update.exe passive /n /f /forcerestart Doing this pops up the dialog box with the command line instructions for the service pack every time. i have even tried it with \update\update.exe with the switches and no love. If anyone has a fix or another way of doing this, please, hook me up. Thanks in advance.

Check out http://www.petri.co.il. The guy running that site has step-by-step guides for just about everything. Thats how I got my AD domain setup with ease. Enjoy.

Here is a fix, graduate from school, go to college, get a degree, apply at said school for the network admin job, block solved.... But seriously, chances are very good that if there was a way around the block, they have already though about it. And if there isnt and you are able to find a was around it, they have stuff in place to detect it and shut it down quickly.

Can't we all just get along???? For the love of God, can't we all just get along?!?!?!?!

Hmmm... well, one thing I that really shouldn't be posted here is that blacklisted WinXP key. I'd recommend editing the post and add all "X"'s for the key. other than that, one of the other gurus here should take a crack at yer code.

Check out MCSE World by Daniel Petri. The guy that runs that site has tons of step by step info on setting up Windows 2000/2003 AD, Exchange, ect.

Hmmm... does having the UnattendMode=DefaultHide still allow you to boot from the cd and perform a repair if needed??

Ok guys, here's the $1,000,000.00 question from me: Is it possible to create a Windows XP Professional VLM that has the VLM key already integrated into it?? my problem is this: ;SetupMgrTag [userData] ProductKey=ABCDE-FGHIJ-KLMNO-PQRST-UVWXY FullName="MYNAME" OrgName="MYORG" With just this minimal amount of info, it errors out during the initial gui portion of the setup. The above is all the info I want to have on the cd. The reason is if I do an unattended winnt.sif (which I have done successfully), I am unable to boot the cd to do a repair operation. Any thoughts or suggestions on this would be graciously appreciated.

You can have any number of members in a workgroup (not sure exactly how many per named workgroup). problem is that each resource (i.e., computer, printer) is limited to 10 concurrent connections at a time.

Using Software Updates Services on an existing Win2k/Win2k3 server can deploy all of the critical updated needed by your workstations. To be more granular, Systems Management Server (SMS) 2003 will do the same as well as the non-critical updates. Ghost really only works well if the machines are of the same hardware type, and as you stated, some are, some aren't. With the SUS and SMS2k3, you can have the updates sent to the workstations without user intervention if i am not mistaken. SUS really dosen't keep easy to read logs of what updates were deployed, but SMS2k3 does have reporting capablilites with it. Hope this helps.

Well, you can use Win2k Pro as a "server", but here is what you will miss out on: 1. Win2k Pro is limited to 10 concurrent connections. After that, any further connections are refused. 2. No domain. You will only be able to run in workgroup mode only. And any other computers connecting to it will need to have an account and password set up on the Win2kPro "server" to establish connections, unless all your shares are wide open (what did you say your ip address was again?!?!?!?!) 3. Granted it would be cost effictive to run it in this configuration, but Micro$oft offers whats called their "Action Pack" in a standard and plus configuration. Standard is $299 USD, Plus is $399USD. with this, you get the following: 1 license for and 10 CAL's: Win2k3 Server Enterprise Win2k3 Server Web Exchange 2k3 Enterprise Sql 2k Developer Win2k3 Small Business ISA 2k Enterprise Mobile Information Server 2k2 Enterprise Sharepoint Portal Server 2k1 Win2k3 Terminal Services 10 licenses for: WinXP Pro Office Pro 2k3 Frontpage 2k3 Outlook 2k3 Mappoint 2k3 Visio Pro 2k3 Project 2k3 Check out this link for more info: http://members.microsoft.com/partner/sales...tionpackus.aspx All said, I myself (when I get my tax return) would get one of those packs, the plus preferrably. Sure, it will set you back the price of a high end vid card, but compare the price of everything seperately. Don't need a slide rule for the end result. Plus you can get to work with an actual server deployment, working your way to that high end server admin job we all covet. Hope this helps, and good luck with whatever you decide.

edit the local group policy on the machine preventing anyone but admins from making changes to the network settings. then go in and define a bogus proxy server ip address (my fav is 127.0.0.1. no place like home). then add your lan ip addresses and any other valid sites said moron... er.. user absolutely need to go to in the bypass proxy settings under tools-internet options-lan settings-proxy server-advanced (i.e., *.microsoft.com; 192.168.*; and so on). this will cause any ie sessions to go to the loopback address if they are not clearly defined in the proxy exclusion list as sites that do not need proxy to get to. or you could just have said persons boss threaten to write them up or worse, but that would make sense. i deal with crap like that every day here at my job. good luck!!