Stoic Joker

Now I've already been through GP and there is a policy that appears to control this...but it doesn't. So... Does anybody know how the hell one is supposed to go about hiding the MenuBar in Windows Server 2008's Windows Explorer? I spend a great deal of time working (multiple desktops) with either VMs or via RDP so screen space is at a premium. I haven't used it (the menu bar) in years as I'm more of a (right click) context menu guy ... So I'd like to have the space it takes up for things I actually need to be viewing. Ideas?

5. Have her start it in safe mode which will automatically display the Administrator account or what ever the Administrator account has been renamed to.

20.19 wpm 95.51 cpm 5 mistakes Never said I was fast...

Look at this as a golden opportunity to throughly document you domains configuration. I maintain a 60+ page word document with complete details of our network configuration. Starting with high-level stuff Model, serial, and service tag numbers for all servers. A break down of which servers host which services, databases, etc. Partition sizes and a rough list of what's on them. Basically anything that might come up as a show stopper at 2am during a bare metal rebuild is all contained in that documentation. I take screen shots of some of the more critical & intricate configurations for clarity and embed them in the document. (The title at the top of the document is Don't Panic! ... and yes it's in green letters ) Do not store the documentation for the server, on the server, because if you ever really need it ... you won't be able to get to it. I keep one copy on my WS which is backedup offsite seperately from the normal offsite backups we do for company data. I also give a printed copy to the company's owner to keep in her files just in case I get hit by a bus ... and they decide to continue opperating without me.

ROFL ... You gota be freaking kidding me!?!

no-ip is just a dynamic DNS utility ... it's up to you to do the rest. Given the 80/81 port choices I'd assume they were using the TS-Web connection. Their router should have the ports (80 & 81) forwarded to whatever internal target IP they used before. Check the SBS server's config to verify what they were doing and just match up the rest. (IP, Port, & TS-Web Connect install if necessary)

Not as secure (at least the old version isn't). LogMeIn gives you 256-bit security, both the remote desktop feature and Hamachi. Encryption is something you have to remember to not get carried away with, as it's only one part of the security whole. Any of the heavily advertised Fetch-My-PC type services are going to get trolled constantly by Script-Kiddies looking for some dope with a simple password. My advice is to use anything except one of these high profile targets. I'll take RDP with FIPS (or a certificate) and a proper password any day.

It's not that hazy! Yes it's (yet another) fork of Two_toNe's TClock2, development on it has been stagnant for over a year as I've been tied up with work. It's still written in C and comes with both 32 & 64bit versions. I don't recall what it was that I'd offered to help with either ... but I do vaguely remember doing it.

That's not actually dumb. I had a client who's server died when the bug guy sprayed insecticide into the back of it and didn't tell anybody. Two weeks later the box croaked as all the boards corroded from the caustic spray. I completely disassembled the box, and scrubbed down all the boards with baking soda, bottled water, and a toothbrush. After letting the boards dry in the sun for 3 hours, I reassembled the box and it ran like a top. Now dumb...is when I took the nuts off the through the case (5lb copper block) heat-sink mount for my dual 3.0 Xeon server, and forgot to hold onto the heat sink. It ripped the processor out of the socket bending **** near all of the pins. It took 4 hours a with square toothpick, and a magnifying glass to straighten the pins...but I did save the processor.

Yes the MS FTP can be secured in that fashion. I would also recommend running the service on a "Bastard Port" (e.g. something other than it's default port 21), to prevent the Script Kiddies from flooding the thing with logon requests.

Hm... How are you entering the username? Just username? or DomainName\UserName? or UserName@DomainName

As I recall Windows Integrated & Digest Auth are not compatable...You have to pick one or the other.

Just for the record, Your D: was a Logical Drive in an extended partition...not a partition. So if you were trying to create a standard partition inside of an extended partition...that's not supposed to work

Password never was stored in the rdp file, nor should it be. I've always just created multiple rdp files one for each machine I regularily connect to (creds stored as needed) and it has always worked out just fine in both v5 & 6. If you're going to Email someone a connector (phone them with the pw), you sure as hell don't want the password embeded where any Tom, Dick, or Harry can grab it and acess the system!

Is this the final/RTM build? It doesn't seem to say one way or the other. I grabbed Pro last night.

That's actually (sadly) normal. Spammers like to flood a domain with huge lists of common names hoping to use the NDRs to identify "live" addresses for a more focused 2nd wave of active spamming. the Access db used by GFi got blown apart in the first 3mo at our office because the spam count went (way) past 4 million in that time period... I gave up on getting reports and am just letting it auto-delete the domain harvesting stuff. Only the keyword filtered stuff goes to an isolated box for further review (e.g. sombody notices something is missing) and just that runs close to 10,000 pieces of spam a week.

I'll stick with my HP LaserJet 2100, as I only print about 20 pages a year (I hate hard copy...).

Answer Q.3 Disable offline files

Vista x64 has been doing just fine for me. Only complaint I have is the clowns over at Zoom don't seem to be able to be able to write a driver for my (3025c) modem, which may result in the modem being tossed in the trash.

Lock Computer: Work=Yes / Home=No - Unless we have company... SS Password=No (I don't use screensavers/just let the screen blank) Force others to Lock comps: I haven't yet...

Some folkes tend to get cranky if you clear their history... So I only start a command prompt from the run dialog, and then launch everything from it...as there is no need to clear the history of events that were never logged in the first place.

Not to mention the fact that if the 2nd DC is not part of the existing domain it will be uselessly unable to authenticate anything if it's put into service. None of the RIDS, PIDS, SIDS, etc. will match and even if they did the machine account creds won't be up-to-date so the logons will still be refused. Always Keep a current backup of System State Data, and do an authoratative restore in Directory Restore Mode. ...That is of course after you do what FAT64 mentioned above . The 2nd DC should be running and online at all times so that it's up-to-date and available when needed. AD is Peer-to-Peer, so they'll keep each other up-to-date ... if you let them.

Making a utility that cripples its way through Windows security is not going to help anyone. You really need to take the time to learn what changes are made between versions, and why the changes were made... That will allow you to get things connected quickly & smoothly. Most common mistakes I see people make: Software firewalls - playing rock-in-the-stream Blank Passwords - Windows won't allow accounts with blank pws to connect over a network (nor should it...)

Try copying the driver files to the (Wizard's default search location) C:\WINNT\INF then the wizard should just "find" them on its own during the upgrade.

Angry IP scanner works well for that type of thing, and is small, fast, portable, & free.