chilifrei64

Are we talking dual boot CD's (Multi-boot CD's) or are we talking Dual boot systems(one box, multiple operating systems) If you want a dual boot system.. make sure you have 2 partitions and install one OS to one partition and install the other OS to the other partition.. If you want a MultiBoot CD then use Windows XP Power Packer.... http://msfn.org/comments.php?shownews=13748 I just played around it it and it works great.... Good work guys

Couple of questions... Before you join the laptops to the domain... what DNS Server is it pointing to?... can you ping this address? After joining it to the domain... what DNS Server is it pointing to? It should be pointing to your active directory dns server as your primary dns server. Can you ping this address? Can the Domain Active directory DNS Server query external dns domains?... Can it ping Google.com? As far as hardware configuration.. this shouldn't make any difference. I know 2k3 DNS servers and firewalls have had a few issues because 2k3 dns servers query dns using packets larger than 512kb and firewalls like to block udp packets larger than that size... but lets get through the basics first..

I think you have your Ideas crossed. Dual Boot and Slipstreamed are 2 different things. Slipstreamed is is when you integrate service packs or updates into an installation CD Dual Boot is when you want to install multiple operating systems to your computer

Port Scanning is exactally what it says it is. If you are fully up to date and running firewall software with no spyware or viruses then I wouldnt pay too much attention to it. People scan entire IP ranges for open ports that they can exploit.. Run a scan on yourself to see what ports are open and research them to see if you are vulnerable.. you can either use a program called SuperScann from a remote location or use http://scan.sygatetech.com/prequickscan.html As the above person.. I too like to use sygate.. Simple, always works, never breaks down.. great product.

Try this program http://tweakxp.com/article37622.aspx

None that I am aware of.. Just reboot later

Yeah... no problem there... should be fine

You could do it using group policy... not sure how you are deploying your workstations but just use the adm file found here with AD and this should help http://www.terranovum.com/projects/energystar/ez_gpo.php and set the settings to like 3 hours or whatever

Actually you know your right... There is a newer version now than the one I took. I haven't heard much feedback on the new one yet.. I am taking the CCNP ones now.... those are gettin a little crazy but i would still say pretty straight forward.... I am really a Cisco guy though.. I just find that kinda stuff easier. Too much marketing and propaganda in Microsoft Certs

Not sure what you are trying to do here. Please explain a little more

The way this is done is Boot to your XP CD When you see the "Welcome To Setup" screen, you will see the options below This portion of the Setup program prepares Microsoft Windows XP to run on your computer: To setup Windows XP now, press ENTER. To repair a Windows XP installation using Recovery Console, press R. To quit Setup without installing Windows XP, press F3. Press Enter to start the Windows Setup. DO NOT choose "To repair a Windows XP installation using the Recovery Console Accept the License Agreement and Windows will search for existing Windows installations. Select the XP installation you want to repair from the list and press R to start the repair. Setup will copy the necessary files to the hard drive and reboot. Do not press any key to boot from CD when the message appears. Setup will continue as if it were doing a clean install, but your applications and settings will remain intact. If you wanted to take the extra step... before you run the repair installation.... boot to like bartPE or an NTFS DOS reader and delete the Default User and All Users profiles from C:\Documents and Settings..... Maybe there is something corrupt in the default profiles.. also remove your ntuser.dat file from your user profile EDIT:Made Color RED for DO NOT

You are able to run a repair installation.. Insert the CD and boot to it... go through the lists like you normally would untel i think it is right after the EULA where it searches for previously installed Windows Installations.... it will detect your c:\windows directory and it will give you the option to run a repair installation.. This should be your best bet...

Unless you specifically set that policy that will not be your problem Are your policies applying AT ALL or just not those specific one.. because then it is a permissions issue possibly

Start -> run -> tscc.msc (or Terminal Services Configuration/Connections) Select your connection (Default:RDP-tcp) and select the Enviroment Tab. Add your application there and it will have the same effect. This is for Windows Server 2003.... I do not have a 2000 Terminal Server to validate this true on 2000 Terminal Server. If my memory serves me correct... it does...

If this is for business use.. use a dedicated machine.. you want the DC to be the DC only if at all possible. If you are just playing around for home use or just to get to know it in a test enviroment then you shouldnt run into and adverse effects by doing so...

Try creating a new profile and see if it does the same.. if you still run into the same problem.... then yeah.. just reinstall

Interesting.. I found the CCNA way more straight forward than A+ and NET+ and Microsoft. I've gotten past them all with M$ being the hardest of them all

So you can log on while someone else is on it.... IE... My wife is on the computer.. i need to log in from work and get something... i can still do that withough interrupting her. And I may be wrong but i think boooggy means by answering the question is everything worked under SP1.. meaning SP2 was the problem.

Internet connection sharing and enable it on the wired box set up an ad hoc connection between your 2 wireless devices

2000 server and 2003 server should have it

Unfortunately, many programmers do not program this way because it is much easier for them to write a program with the user being an administrator. I have successfully gotten this to work at one of my clients but we are talking about weeks upon weeks of testing software and assigning permissions on registry keys and setting user rights assignments in group policies and all sorts of other crazy stuff. What they are talking about in that article is that microsoft knows that programmers are not writing code for least privledged user and they are trying to make it easier for programmers to write programs this way. We shall see if Microsoft succeedes or fails on this front in the next version of windows. Not on windows XP or 2003

you should be able to retake ownership of it then resetting the permissions on the drive

Try strat -> run -> gpedit.msc -> Computer Configuration -> Administrative Templates -> system -> logon -> Always wait for the network at computer startup and logon -> set to "Enable" Or you can run a simple Net use batch script to remapp them at logon. This happens when lets just say the computer boots so fast that the network hasn't gotten a link or an IP address yet.... which reminds me.. you could also try setting a static IP if you didnt want to do the other two... that MIGHT work for ya.

Then you only have windows XP home edition.. you will need to upgrade to Windows XP Pro

I double checked my settings and yeah.. that setting works for me to and my users cannot do it