clutch

That's pretty cool.

I have been using SMS for the last couple of years, and in general I tend to do what you mention; I will simply deploy a batch file and run it as an admin (if needed) with domain admin credentials. You can also use WSH scripts to do more advanced functions assuming that you have a fairly current version of WSH on the workstations. If you have that kind of hardware, I am assuming that you have a decent test server/client base to play with and can practice the pushes on that. You'll find it's really nice, but sometimes hangs on advertisements a bit for no apparent reason, so if you set one up and it never goes out, just recreate it and you should be fine. Also, another thing, if you plan on distributing an application (like SP2) from one site, bear in mind that it will still make a copy of it to distribute it anyway. This is kind of annoying, as the server is also my only CAP (small network) and I wind up with 2 copies of it. This behavior eats up disk space quickly when you are pushing apps the size of Office 2000.

All Windows NT OSs have 10 concurrent connection limits, so you will be capped to 10 regardless of version (NT4, Win2K Pro, WinXP Pro). I would not suggest that you use it as a server because hitting that cap can get really annoying (I had to do it in an emergency, and it's very easy to run up 10 connections).

I think that if I wasn't such an IIS addict, I would look seriously into Apache.

hahaha I had forgotten about this one already...

Actually, that's pretty cool. I used to leave redirect links and requests to go to the original post, but there were a few times where you could see the same post 3 or more times and that got pretty old quickly.

Honestly, I am not sure I follow what you are saying, but I did post my reasoning earlier and many other people seemed to agree with it. In a forum where you can easily post a link to an existing issue, I don't see why the discussion can't be held in one forum and linked from others, so that many people can take part in the same topic at the same time rather than bouncing back and forth between them. It seems much simpler to me, but if you find this an easier way for people to respond to a topic then more power to you.

Actually, it does make a difference if someone is interested in a thread and responds to it, not knowing there is another one that's active elsewhere. If you link to your original one, then all the responses can sit in one spot and each person can see what others have posted. Not such a pathetic reason afterall, now is it?

Just an update to my last post; I got this today in my Windows.NET newsletter, and the following explains in more detail what the next file systems will be like: Quote: Windows Longhorn, the client and server OS that will follow .NET Server, is even more interesting than its predecessors. Although most Longhorn server-specific features remain a mystery, many of the release's client features are important to the enterprise. Chief among these features is a new SQL Server-based file system called the Universal Data Store (formerly code-named Storage+). The store will obscure the physical location of files and folders and present a simpler, more logical way to store user data. According to Microsoft CEO Steve Ballmer, you shouldn't think of the store as a file system anymore: It's just a data bucket. Longhorn users will be able to use XML-based SQL queries to search for data. And they'll be able to send search requests remotely, giving this technology many benefits beyond the desktop. Microsoft is working to consolidate its data stores using the next generation of SQL Server, code-named Yukon. Longhorn and the next generation of Microsoft Exchange Server and AD will be based on the Yukon data store, so administrators and users will be able to query these disparate data sources at the same time. Currently, the Windows file system, AD store, Exchange Server mailboxes, and SQL Server databases are separate data buckets: Although custom solutions exist for aggregating searches of these stores, this functionality will soon be a feature of the OS. However, the inclusion of Yukon technology in Longhorn will delay the OS's release until late 2003 or early 2004; it was originally expected in late 2002 or early 2003.

I got this in my "myITforum" newsletter, and Lactic is passing it around another forum. http://www.poenews.com/inhouse/vx2.htm It also shows how to get rid of VX2, so you might want to check any systems you have control over.

Wow, this is much better than waiting for updates to Trillian when AOL jacks them... So, now we add another step AND application to the mix eh? You are dedicated to your method, aren't you?

Try to FTP it from a remote computer, and then tell me. With all the file status requests, it takes quite a long time vs. using one simple file.

Just got this today, and thought some of you with way too much time on your hands might want to submit your opinions as well. http://www.survey-poll.com/email/1837mtu.html

@Felix, Been watching "Connections"?

Every time I install a system, I export my favorites and cookies and just bring them over to my new system. They import very easily, as they are just 2 files (as I have almost 600 bookmarks in 100+ folders, that helps me a bit) to keep track of. Also, he asked how to export them into a single HTML page, which the copy and paste method wouldn't accommodate anyway.

"It's impossible." Now you can add another one to that list...

While I am not sure what the specific error will be (simple failure to copy the db because it's open, connection drop due to Win2K file locks being present, db corruption, etc), I would have to say that it would not be successful. Is there any way that you can batch run a backup and sync that? Most current db systems (like MS SQL) have many methods of syncronization that can be done in different ways, like nightly backup and sync jobs or transaction-based where it will update the slave database after each successful transaction. Also, are you using master-slave or merge syncronizations? The backup and transfer method would work much better with master-slave than with merge (and may not work at all on many db systems).

This is my fav, been using it for a long time now: http://www.mlin.net/StartupCPL.shtml

No cross-posting please. Anyone looking to respond can go here.

Thanks guys...

I got this in a weekend update from my MyITForum newsletter. I added the last one, since it was something I always see in every TV show and movie. Things Computers Do in Movies Word processors never display a cursor. You never have to use the space-bar when typing long sentences. Movie characters never make typing mistakes. All monitors display inch-high letters. High-tech computers, such as those used by NASA, the CIA, or some such governmental institution, will have easy to understand graphical interfaces. Those that don't, have incredibly powerful text-bases command shells that can correctly understand and execute commands typed in plain English. You can infect a computer with a destructive virus by simply typing "UPLOAD VIRUS" All computers are connected. You can access the information on the villain's desktop computer, even if it's turned off. Powerful computers beep whenever you press a key or whenever the screen changes. Some computers also slow down the output on the screen so that it doesn't go faster than you can read. The *really* advanced ones also emulate the sound of a dot-matrix printer. All computer panels have thousands of volts and flash pots just underneath the surface. Malfunctions are indicated by a bright flash, a puff of smoke, a shower of sparks, and an explosion that forces you backwards. People typing away on a computer will turn it off without saving the data. A hacker can get into the most sensitive computer in the world before intermission and guess the secret password in two tries. Any PERMISSION DENIED has an OVERRIDE function. Complex calculations and loading of huge amounts of data will be accomplished in under three seconds. Movie modems usually appear to transmit data at the speed of two gigabytes per second. When the power plant/missile site/whatever overheats, all the control panels will explode, as will the entire building. If you display a file on the screen and someone deletes the file, it also disappears from the screen. If a disk has got encrypted files, you are automagically asked for a password when you try to access it. No matter what kind of computer disk it is, it'll be readable by any system you put it into. All application software is usable by all computer platforms. The more high-tech the equipment, the more buttons it has. However, everyone must have been highly trained, because the buttons aren't labeled. Most computers, no matter how small, have reality-defying three-dimensional active animation, photo-realistic graphics capability. Laptops, for some strange reason, always seem to have amazing real-time video phone capabilities and the performance of a CRAY Supercomputer. Whenever a character looks at a VDU, the image is so bright that it projects itself onto his/her face. *Computers are always scrolling something. The more things that are scrolling in the background, the more important the computer must be.

Do they have to copy these files over and over again at logon? Is there a need to keep that line in the script? Are these files ever in use by other users/programs besides at logon? Does it go faster if you use the UNC to the share rather than the newly made drive map from the script (just use \\server\share\*.* rather than p:\*.*)? One more thing, try putting the files in question in a folder, so the line in your script would read something like p:\somedirectory\*.* instead of copying from root. I have some programs that hate copying from the root of a drive as you are doing in that script.

Women.

Yep, just follow the normal export method in IE and you will be fine. Open IE, go to File>Import and Export, and then select export bookmarks. You can export portions of your favorites (like this this subset of my main list in IE) or all of them, and get a webpage to come out of it.

I don't even know why ServerWorks would be an option, since most people don't know that they even exist, let alone what level of chipsets they offer.