DS3Circuit

a good impression adamvjackson Back when we used OL 97/98/2000 as a POP email client, there were many a time when users needed to recovered deleted emails or getting at PSTs where they couldnt remember their password. At the moment, I am not too fond of Exchange's brick level backups/restores. At least veritas plugins make backing up the IS relatively easy.

Disable your antivirus, and any Norton programs that may be protecting your system. Also, you may want to defrag your hard drive. Your Recycle Bin may be full or corrupted. Either set the Recycle Bin to hold more or empty it. Just a couple of thoughts that come to mind

Thanks for re-activating my account Phillip -------------------------------------------------------- For those who are curious about why there is such a discrepancy in PST sizes, I figured I would throw this in. A PST is a database. Items are records within the database and there is an index that points to each item. When you empty the Deleted Items folder, Outlook doesn't actually delete the items, it just deletes the items' listings from the index. The item is still in the PST, but unrecoverable because Outlook has no idea where it is without the pointer in the index. The space the item takes up is called "whitespace". When you Compact a PST, the item is finally removed permanently and the whitespace is recovered, often shrinking the PST by many megabytes. Once the PST has 20% "whitespace", Outlook begins compacting the PST. If the Deleted Items folder contained a lot of messages, Outlook may begin compacting the PST immediately and the items will be deleted forever within a few minutes.

The date setting in the registry for the installation date of the OS for NT is located in "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\InstallDate". The values displayed are the following example: 0x39c24d62(969035106). InstallDate REG_DWORD Time (in seconds) since 12:00 A.M. on January 1, 1970 Stores the date and time that the current build of Windows NT was installed. For example, Monday, January 01, 1996, 12:00:00 AM would be 0x30E76A50 (820,472,400 seconds).

www.appdeploy.com should be your first stop as adamjackson has pointed out Wise Package Studio is the best way to create MSI installations. I have used this in numerous bank roll outs. If you want something far cheaper you can use MSI wrappers to install applications. http://sywan.nl/forums/forum.asp?FORUM_ID=15 Sorry if this was the main focus of this thread, I was reading the last posts.

Server OS? Service Pack Level? Do the same symptons appear on the clients when directly connected to the printer as TCPIP printers, instead of mapped printers? What type of HP printers? We have had numerous problems with the 2200DNs and have reverted back to the Laserjet4 driver. The laserjet 4 driver is the most basic as stated by some of my HP reps, and any HP printer can use this driver. Switch it around to see if that helps. Event logs show anything?

Im gonna throw in conf.exe or Netmeeting as a viable way to remote control a machine

Have you seen this KB article? http://support.microsoft.com/?kbid=317367 HOW TO: Use the Group Policy Migration Utility to Migrate Windows NT System Policy Settings. Though I imagine only the policies that 2000 uses will be able to migrate successfully over. You may have to create your own ADM files for GPOs. I have used mandatory profiles in the past, but I have never had one for dual platforms.

What you are asking for can be done with exchange 2000 and event sinks but like what sapiens said, if this is the primary function, I would invest in HelpDesk Software. We use http://www.epicor.com/ with a SQL2000 backend.

Systems .... yes Exchange .... Domino .... Groupwise If multiple clients need to access a single flat file, then they need full RW privileges, which is not possible with Outlook, Outlook Express, Eudora, Notes. (Unless I am missing something) Sorry, I havent worked with any other clients.

Few more helpful links How to Use Dumpchk.exe to Check a Memory Dump File http://support.microsoft.com/default.aspx?scid=kb;en-us;Q156280 Gathering Blue Screen Information After Memory Dump in Windows 2000 or Windows NT http://support.microsoft.com/default.aspx?scid=kb;en-us;Q192463 Download Pstat here Pstat.exe: Process and Thread Status http://www.microsoft.com/windows2000/techinfo/reskit/tools/existing/pstat-o.asp Dumpchk.exe is part of the windows 2000 support tools found on your CD of windows 2000. Keep in my other required files include Kdextx86.dll and Msdis110.dll Anything else I can help ya with?

www.sophos.com ---> Excellent www.trendmicro.com ---> Better Than Excellent http://www.trendmicro.com/en/products/global/enterprise.htm (That and my sales rep is pretty sweet on the eyes ) And then there is the cream of the crop though $$$$$ http://www.sybari.com/products/ Antigen hauls serious $ss a few of my associates say. :-) Best bang for your buck .... trendmicro Did you still need that P3?

44

Seems to be a hardware / driver issue. All drivers been updated to the latest? This has helped me before with INTEL NIC drivers. http://is-it-true.org/nt/atips/atips300.shtml

You talking about this? from ntbugtraq.com Duhmez you need to migrate man Microsoft is aware of a problem with the recently released security patch MS03-029 (http://www.microsoft.com/technet/security/bulletin/MS03-029.asp) This patch corrects a Moderate rated Denial of Service security vulnerability in Microsoft Windows NT 4.0 Server. Specifically there is a problem with the patch when installed on systems that are also running RRAS (Routing and Remote Access Service) that causes the RRAS Service to fail when the system is rebooted after applying the patch. It is important to note that the security fix itself is unaffected and the patch is still effective in correcting the DOS flaw. Microsoft is investigating this problem and will shortly issue a fix to correct it once that fix has been thoroughly tested. The security bulletin has been updated to reflect this. In the meantime customers affected by the problem may take one of the following actions. 1. Contact Microsoft Product Support Services for a hot fix that corrects the problem. This fix has not yet been extensively tested and should therefore only be applied by customers who are directly affected by the RRAS problem. 2. Install the patch if you do not need the RRAS service. The RRAS Service will fail to start however this will not impact normal operations other than those that use the RRAS Service. 3. Review the security bulletin and assess whether your enviroment requires the security patch. 4. Wait until a fix for the RRAS problem has been fully tested and released. The security bulletin will be updated when this happens. Regards, Microsoft Security Response Center

http://support.microsoft.com/default.aspx?kbid=327148 Check your event logs for Event ID numbers? Any particular time your computer receives this "pop up?" ... a triggering event? Did you run an AV scan? For those who need an explanation of what RPC does, well .... here is a brief synopsis. An RPC service configures itself in the registry with a universally unique identifier (UUID) (similar to a globally unique identifier [GUID]). UUIDs are well-known identifiers, unique for each service and common across all platforms. When an RPC service starts, it obtains a free high port and registers that port with the UUID. Some services use random high ports; others try to use the same high ports all the time (if they are available). The port assignment is static for the lifetime of the service. When a client wants to communicate with a particular RPC service, it cannot determine in advance which port the service is running on. It establishes a connection to the server's portmapper service (on 135) and requests the service it wants by using the service's UUID. The portmapper returns the corresponding port number to the client and closes the connection. Finally, the client makes a new connection to the server by using the port number it received from the portmapper. Because it is impossible to know in advance which port an RPC service will use, the firewall must permit all high ports through. If your firewall permits this, there is very little reason even to have a firewall... In the end, no matter how secure your PIX, Checkpoint, Raptor, ISA, Sonicwall, etc firewall is, you need to patch this hotfix.

http://www.cert.org/advisories/CA-2003-19.html Here comes another Nimda ...... Block your ports Patch your NOS Defrag your disks Hide your women and children

Why not just block them as applications that arent priveleged to run under that user context? GPO User Configuration Administrative Templates System Don't run specified Windows Applications HTH

How to Configure an Authoritative Time Server in Windows 2000 http://support.microsoft.com/default.aspx?scid=kb;EN-US;216734 Windows Time Service White Paper http://www.microsoft.com/windows2000/docs/wintimeserv.doc The basic gist is to run set your time service to an external time server. The first link above will show you how. Quote: SNTP defaults to using User Datagram Protocol (UDP) port 123. If this port is not open to the Internet, you cannot synchronize your server to Internet SNTP servers. Remember this if you are behind a firewall. If problems persist, create a batch file to fix this for ya and leave it in the startup ..... we had this issue with some 95 clients,

First off I would read the Active Directory Cook Book http://www.microsoft.com/technet/treevie...plan/dommig.asp This works well for a single domain. Some things to watch: - make sure you know how you're going to handle DNS - whether you're going to use existing DNS servers, which servers will use Microsoft's DNS, whether you want AD-integrated DNS or not (you do!), etc. - If you have mixed NT4 and W2K/XP clients, and if you rely on NT system policies for them, know what you're going to do with GPOs for the W2K/XP clients - if you'll have NT4 BDCs for awhile, have a plan on how to keep the Netlogon replication in sync between the W2K DC environment (which uses FRS), and the NT4 BDC environment (which uses LMRepl) - After you upgrade the PDC and add a second DC, consider moving the FSMOs to the second DC, removing the first one (old PDC), and rebuilding it. I feel more comfortable in having 'fresh-built' instead of 'upgraded-OS' servers, but that's up to you. - add an additional BDC ahead of time, let it replicate, and take it offline before upgrading the PDC "just in case" - TEST the process in the lab, more than once, before doing it in production - that's how we learned about most of the above. Regarding horror stories, I have none. Testing, preparation, and a little luck have gotten me and my staff through several migrations. If you have more particular questions, feel free to post.

Yeah known P3 slot one steppings are cA0 cB0 cC0 B and C are known to support SMP

Depends Do you need a certain P3 stepping as well? I would ship to San Jose, just need to go looking through my stuff

http://www.bootdisk.com/ There you will be able to get the components needed to create a network bootdisk. 1. Copy cabs over to a network share on your server ..... fat32 based partition with only share permissions. 2. Download / Customize your bootdisk so that it allows you to log into that share. Other alternatives include an old parallel port zip drive and running GUEST from DOS. G'Luck

http://www.microsoft.com/windows2000/server/howtobuy/upgrading/default.asp http://www.winsupersite.com/showcase/win2k_upgrade.asp

LOL Now where was that when I needed it several months ago!?! Thank you for that link.