This is not a dumb question, it's a great question and I'm glad that you're asking.
Make sure that you've reviewed all documentation, talked to the greybeards, and have sign-off from someone from the business.
Get a complete backup; mark the media for long-term archival. Run a connection monitor or packet sniffer for a ...
You will need to modify the group policy that is applied to the servers. Open up the Group Policy Management Console and navigate to Computer Configuration >> Administrative Templates >> System and select "Display Shutdown Event Tracker." Disable that option.
While Windows Server 2003 was a very good Operating System for quite some time, it will reach its End of Extended Support life on July 14th, 2015.
While mainstream support gives you free security updates, service packs, non-security related hotfixes and a wealth of other stuff, the extended support phase reduces this to security update support and no new ...
This might be a problem with MySQL notifier config file. As described here, there is something wrong with your config file. You just have to remove it (or rename it to something else) and launch the MySQL notifier again - config file will be recreated automatically.
In my case, the config file was in the C:\Users\YourUsername\AppData\Roaming\Oracle\MySQL ...
Power it off and see who screams, and about what.
Seriously, it is the best way. Even checking logs will only get you so far, because you'll only see activities that are logged.
EDIT: To head off any further comments, this advice assumes you've already done what you should have done in the first place, even before asking the question here - asked around ...
Running the following as an elevated admin:
reg.exe add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Reliability" /v ShutDownReasonOn /t REG_DWORD /d 0 /f
and then logging off and on again should to the trick.
This is quicker than using group policies which you should use when you are in a domain and want to apply this change to many servers.
I totally don't want to discount the rest of your question, but the path of least resistance is to replace the failed disks.
When dealing with legacy equipment, there may be a temptation to devise an esoteric or clever workaround, but your immediate goal is to keep this particular hardware running in the current and stable state until you can migrate ...
It certainly can work, but this is one area where it's entirely dependent upon your code. It may work, or it may not.
This is where doing a test upgrade would be a good thing to test out.
Deploy the app in a new Server 2003 instance in a VM of some kind.
Upgrade it directly to 2012.
Figure out what needs to change to make it work.
Repeat 1-3 until you ...
You should set up a domain.
Seriously. I wouldn't want to manage 3 Windows computers without a domain (Active Directory), let alone twelve.
If the brass wants to limit the access levels on certain directories, the only way to do so in a manageable fashion is with Active Directory, even for "only 12" machines/users.
Best option for you, personally, as ...
I really wouldn't bother upgrading anything to Server 2008 now, given that there are two newer major versions of Windows server that have been released since.
Your choices are really between 2008R2 or Server 2012/R2, at this point. I would advise that there's probably very little point in seeing how it runs on one version before trying to move it to ...
Use netstat -ba in administrator level command prompt, and you will see all active network sockets and processes that own those sockets.
-b tells netstat to output executable name of the socket owner.
-a tella netstat to list all listening and client sockets.
There are settings in the Server 2008/2012 policies that aren't accessible on your 2003 server I believe, such as "Do not connect to any Windows Update Internet locations" under the Computer settings you show above.
I believe the settings you are looking for in a 2003 environment are:
Disable access to Windows Update
The correct policy for v6 ...
The command you mentioned is fine and almost reaches the goal you've set. If you really would like to perform the 1:1 migration, I would suggest you to consider following options:
robocopy "\\Source server\folder\" "\\Target server\folder\" /MIR /COPY:DATSOU /ZB /R:1 /W:10 /TEE /log:<log path.txt>
/MIR - this will MIRror a directory tree - whatever ...
You might be surprised by the response that you get from Microsoft support, since this problem seems to not be so much about supporting Server 2003, as it is about a roadblock that's preventing you from moving to 2012 R2. At least, you should spin it that way.
I am also almost sure that this is due to schema customization. It's usually by 3rd party software,...
Event Log Consolidator
View, consolidate, and dismiss event logs and correlate issues across multiple systems
Tired of having to open Event Viewer and connect to each Windows system to see its event logs? Don’t have a centralized way to view events from multiple servers?
Download SolarWinds Event Log Consolidator to organize event logs from several Windows ...
I, too, ran across this problem on my local install of MySQL Notifier, and neither deleting settings.config, nor reinstalling had any effect. Further investigation lead me to a file in the same folder with the name connections.xml that only contained a single space character. Deleting that file and restarting the notifier did the trick, though, so if (like ...
I'm sure the OP has found the other answers useful but future readers may be interested in a powershell version. Works out of the box in 2008 or up, and maybe in 2003 if powershell is installed.
if ( -Not (Test-Path 'registry::HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Reliability'))
New-Item -Path 'registry::...
The bottleneck I see when accessing that URL is clearly due to the window size.
When I try to download from your server I get 555KB/s. I have a roundtrip time of 108ms. Doing the math I get the following window size: 555KB/s * 108ms = 59.94KB.
As long as I do it from a host in a datacenter, I get a very consistent throughput and roundtrip. Additionally, if ...
Why are your users browsing somewhere that they can see this in the first place? There are a few things I'd like to address, so bear with me.
It appears you're using a domain controller as a file server if your users are seeing NETLOGON and SYSVOL. Don't do this. Have your domain controllers run AD DS, DNS, and nothing else if at all possible.
You don't ...
Active Directory does not really concern itself with how the User account object's RDN (the last part of the Canonical Name) relates to other properties like the Display Name or the Logon Name - as long as the value of each individual attribute doesn't violate the schema definition.
The behavior of the "New User" form in Active Directory Users and Computers ...
First off, only administrators should get admin access so unless there is a HUGE (I can't think of a good one) reason they need it, then it should be left to the admins; there are rare occasions when a regular user gets admin privs, and even then I'm usually skeptical about why they need it.
Second, you can accomplish what you want to do by using Group ...
After starting your first instance of PSEXEC.EXE as the LocalSystem account, include the local computer's IP address in the command to start your second PSEXEC instance, like this:
PSEXEC.EXE \\LocalComputerIPAddress -u DOMAIN\my-user -p mypass CMD
The behavior you're experiencing is due to a new security feature added by Windows Server 2003's ...
Forest and Domain are two separate things.
Open the Active Directory Domains and Trusts MMC. Right-click on the top node in the tree (Active Directory Domains and Trusts [yourdc]) and pick "Raise Forest Functional Level...".
You can get the list of what users are currently in the Administrators group with:
net localgroup administrators > userlist.txt
You can then split the users from that output into tier1 and tier2 lists and loop through the lists.
foreach ($user in get-content $tier1file)
VL stands for "Volume License", and you need if you have a VL key.
What you should use is "None". Win 2003 Server will be out of service in a year and it doesn't make any sense to start any project with this old piece of software.
So I was curious enough about this one to research it out. I don't have a 2003 server environment to test on, so it was up to "Google Fu" to check into this.
Turns out it is a "bug" in the GUI. The policy you applied did work correctly, it just doesn't show up correctly in IE's GUI on the client. Stupid, yes...but true.
Here's an example accepted ...
For users who are authenticating against the server with LDAP (file shares, print shares, etc.) you can use the "Shares & Sessions" snap-in in mmc to identify users who are connected with open sessions. These are users who are actively or passively (mapped drives) connected.
I found an article that is more detailed.
You can also check if it has any ...