Malkosha

When the compnay I worked for split into 2 groups I had to move my users to another domain. I copied the current domain profile to the administrators profile. I then changed domains on the PC, logon as the new user on a new domain, then copied the profile back. This gave me: Mapped drives, printers, desktops etc. I created a new outlook PST and imported the settings from the old one which was on their drive. I then copied favorites. I lost the cookies of course. I had to reconnect the mapped drives, becuase the user had changed, but it was easy considering the drives were already there ... they just didn't have permission to access them. This saved me a ton of time, and I spent about 10min's per PC, depending on how big their PST was (if you don't watch them, they will grow ... one user had a 450meg PST). Another cleaner way is to work with roaming profiles, but that would only be good for you in a future change. Luck!!

I'll take a stab at this one. What you could do, is setup a new local account, on the workstation. Then copy the current user profile over to the new profile. This should preserve most of the settings. Later, when the user is up, copy the profile back. You will have to re-map any drives since the SID has changed, but the drives all already there so no problem. I'm not sure about cookies or fav's but they may also work. Luck

Trying to keep this short, We have a main office with a PDC and BDC, along with 6 locations that have a BDC. We use cisco routers with NAT enabled. All are running NT4. We upgraded the servers at the main office to Win2k. DDNS was a learning experience, but we got there. When we tried to upgrade the remote BDC to Win2K, we couldn't establish the trust needed with the Win2K servers at the main office. We played with DNS and still couldn't get it. We ended up calling MS and they said that the problem is that Win2K can't/won't validate or establish trusts through NAT. In other words, as long as NAT was in place internally, there was no way we could run a Win2K network. Has anyone else run into this problem, or better yet, is there a workaround? I would hate to re-design the entire network in order to upgrade to Win2K. Thank you!

We upgraded our DC's from NT4 to Win2K. Everything seems to work ... except for one little problem. Our RRAS is on one of the DC's, and when ever someone RAS's in, they get a DHCP address. This address is then picked up by DNS, and the DC is assigned that address. Of course, all connections to the DC are lost. By deleteing the DNS entry and stop/start the RAS service, the problem is fixed ... until the next time someone RAS's in. Anyone have a clue how to fix this?

Thanks but, it is static. What seems to be happening is that DNS asigns the RAS address to a DNS address. This confuses the NT4 machines. Oh .. I forget one important point. This only affects machines that are not Win2K or XP. That is, it only affects Nt4 clients and Win95/98 clients. **edited for spelling errors worse than usual **

I need a little help with Migration from NT4 to Win2k. We have a main office which hosts the Primary and Backup Domain controllers. We also have a WAN with 6 offices that contain BDC's. Each office has a router and at the main office there is a PIX firewall between the main office and the outside world. All of these are running NT4. We upgraded the main office's BDC to Win2K server, made it the PDC and used AD and DNS. The original PDC will be upgraded in a day or so, and we will then convert that into its original function as a PDC. We also want to upgrade the WAN locations but have run into a question. We have WINS working great at the moment, and replicate it one way so the NAT translation doesn't hose the PDC WINS database up. The main office is set at 172.30.x.x while the WAN is set at 192.168.x.x. The WAN computers communicate with the main office using 172.17.x.x as the translated address. The PIX is set so no one can ping the PDC from the outside. What can we do to allow DNS to handle name resolution (and replicate it) without getting the servers all confused? We had this problem with WINS, and solved it by only replicating it in a single direction, create Static mappings, then turnning on MIGRATION (To prevent static mappings from being overwritten). Can this be done with DNS? Thank you!!

Thanks clutch. We had a similar idea, but no where near as detailed or complete as yours, and we left a few things out . We will give it a go! Once again, thank you

Do they make PCMCIA video cards? It would seem that a market would exist for one. While my ATI rage mobility works OK, it would be great to be able to upgrade the video card for higher graphics performance.

Try getting rid of the mapped drives ... they should not be needed. Also get rid of the /v (I assume verbose) and replace it with /e which answers yes to all questions) Nothing to lose heh!

I just installed a new Dell Laptop for one of the company exec's. It has an onboard NIC and it worked fine. However, when his Port replicator came in, I installed it and it had its own NIC card. This was no problem for Win2K of course and the card was found a recognized. We use DHCP on our domain, which gives the IP, gateway, DNS servers and WINS. This is an NT4 PDC. The first card had no problem (LAN1 under network/properties)getting a WINS address and therefore had no problems connecting to mapped drives. The second card (in the PR, called LAN2) only gets an IP address and can't resolve names ... no mapped drives etc. When I run IPCONFIG, the 2nd card shows no WINS address. When I try to connect to mapped drives using UNC names, I get the device is in use error. While I would love to just disable one of the cards and let it go (probably the internal one) the user needs it for going to different WAN sites and logging on. Any idea how I can solve this issue? I guess I could give that card a static IP but thats not a popular idea around the shop. Any ideas? THX!!

Thx!! I'll give it a try .... changing the binding order that is. I have an A20P thinkpad that uses a pass through port replicator, which of course causes me no problems at all. I wonder what Dell is thinking sometimes when they do some of the things they do. For instance, they have the classic "IBM nub" for mouse control but also have the touch pad and 2 sets of mouse buttons just underneath it. At first you would think "hey great! I get options here" but in truth, while you can disable either device (but not the buttons), if you choose the nub then its easy to mistakenly hit one of the "mouse buttons" usually at the wrong time. Thx again!

I updated the drivers for my V3 and they installed perfectly. So did the tools. Everything seems to work great. Get the latest drivers from 3dfx and let it rip.

the problems with Voodoo3 cards that the other betas had? The drivers released from 3dfx didn't load before. While this may be a driver problem and/or a 3dfx problem it seems to me that forcing a rewrite on drivers every time a new system comes out is poor quality control and a lack of vision.

Thanks I will!!

I beat ya to it!! I layed down RedHat 7 and its faster, comes with a couple of GUI's that rock the house and they have no intention of forcing people to "activate" a damn thing. Everytime MS puts out a new OS its the same thing ... need newer/powerful hardware, the drivers are not backward compatible and they charge a fortune. RH7 is the best OS I've ever put on, bar none. With KDE and Gnome pre-installed managing your system is a piece of cake. The GUI's are also skinable and it runs with yesterdays harware just fine. I have Q3 up right now and the drivers for my Voodoo3 work outstanding. MS screwed up with this activation thing and it will be interesting how they will handle it over the long haul. If you think you have problems now ...

When I right click on a file/folder I expect to see a security tab that allows me to set permissions. Mine is not there. Is this a bug? A feature? Do I need to run a utility now to do this? The drives I have are fornamted NTFS. Thanks!!

Divide and conquer. I would fdisk then format your drive. I would startup with a bootdisk that has CD support (win98 startup disk is good for that) and xcopy the I386 dir from the CD/DVD to the harddrive. I would then remove all my devices except: Video card, harddrive, floppy. Everything else I would remove this means cd/dvd, sound, modem etc. Go into the BIOS and use the set up default mode. Try to run setup from the Harddrive. See what you get. This may sound drastic but you have to narrow down the choices. This gives you a barebones system to work with. Good luck!

How much of a change to the hardware before a re-register remains to be seen. I have yet to see the limits or scope of such change ... or than speculation. If you have concrete information on the exect specs from MS on such a change please let me know. I'm suer it will ease others in their decisions. Agreed, intel didn't lose becuase of the processor serial nimber because they changed it before mass production started. In fact it was televised on every news station. Why? People want their privacy. No thats wrong ... they demand it! While MS may not care becuase of all the $$$ they have, if enough people scream will they not listen? Then again if your the king of the world who cares heh! The reason I've brought up Intel and tied it to MS is the simple fact that people want their privacy and will moan and groan to get it. They will also will not purchase a product becuase of it. Lets face it, how many people out there; who BTW know little of this activation scenerio, will say "I'm not getting that so MS can look in my machine". When in fact they aren't really looking (I hope) at all. Its a users perception that will sell this product and you know how that goes. If youv'e worked with enough users you know what I mean. I think that MS is one hell of a company. Unlike some, I feel that they put out great products. I also think people need to remember that this isn't DOS. The more complicated a system the greater the potential for problems. Also the greater potential for abuse. There will have to be some way to monitor the business end of this because as you say, if corporate America has a different version that dosn't require registration it won't be long before Johnny ***** is running it too. Kinda defeats the purpose of it all dosn't it?

Just my .02 I love XP so far. It plays my games well after I sorted out some driver problems. The problem I have is the activation code they plan on using. To have to call MS when enough hardware changes are made (if I understand this right) is a true disaster for what promises (and appears) to be a killer OS. If they tighten the activation any further then I won't go to it. That sad for me because I pickup every new OS the MS outs out. I have a major problem when I spend money for a product and then be forced to register it. That should be my choice. The company I work for is keeping a close watch on this and if nothing changes then Win2k and Off2k will be the last new MS product we buy. Remember the stink about PIII's. Lets see if MS is as smart as intel.

The point here is that if its "dead" or not, many users still have ISA boards they want to use. If your going to make an OS then leaving a segment of the population out because it dosn't fit into your (MS's) sense of standards, then it will limit sales and bring some harsh comments. BTW, my sound card is ISA; soundblaster 16, and I like it because: 1) I don't give a crap about "super" sound and 2) Its compatable with everything. XP dosn't find and install it but I can install it using the WDM drivers after setup. If your NIC is NE2000 compatable then a generic driver should work.

OK. Heres the scoop. In the other versions of Windows anyone can see the NTFS permisions but only administrators could change them. I found that even though you have admin permissions, only the ADMINISTRATOR logon will let you change/set/see them. I had to logon to change mine.

Its not there. All I have are general/sharing/customize. Hmm..let me check my services.

I had some problems with 2419 and my Voodoo3 AGP card on my K62 system. When I installed the drivers it would reboot into a 4bit screen and I had to rollback (great feature BTW). I assume that it has to do with the MB chipset (VIA) in combo with the OS and 3DFX card. I also noticed that many others had this problem. Oh well thats what Beta's are about. Has anyone had any problems like this with build 2428? Are the drivers more complete and functional than in previous builds? Any problems installing the Win2K drivers? While I'm aware that while 3DFX (nvidia now) is responcible for the drivers, the built in drivers should at least be able to perform some basic functions. If not then perhaps MS shouldn't include them at all. I think its to easy sometimes to blame the card companys for driver problems when in fact if the OS's where designed with driver compat in mind it would save everyone alot of work and headache. Then again, if everything worked great all the time I would be out of a job

First of all thx to everyone for their help. I finaly got it working with the exception of the tools. This is what I did: I ran the driver update and installed the latest version of the Voodoo3 drivers. When I rebooted, it put me in 4 bit color mode. I rolled back the drivers and after that it worked fine. Q3 ran great as did my D3D apps. I didn't test any glide apps yet. More than likely, it always worked when I rolled back the drivers but I assumed (ya we know what that means) that since the drivers didn't work the roll-back returned my system to its default mode. This may be a false assumption. There seems to be new reg entries esp concerning the openGL drivers. It seems from this uncontroled test that the roll-back didn't competly revert the reg settings. Its almost like the roll-back only involved the entries/drivers that the original driver set "knew" about and ignored any setting that where not contained in the original inf/pnf. I'm going to try to re-install the OS again for a freah start and compare the 2 reg's for any chages during this proccess and make a more accurate recording of what happens. This is all speculation of course since I didn't document this proccess. Once again, thx for the help and ideas.

I thought of that to friend. Since you need to reboot after the driver change, and before the tool install just the drivers caused this problem. An earlier driver version maybe?