Tag Info

Hot answers tagged

28

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 ...


4

The command tlntadmn -s will list information about the current Telnet sessions. This will display something like the following: C:\Windows\system32>tlntadmn -s 1 telnet session(s) ID Domain UserName Client LogonDate LogonTime IdleTime (hh:mm:ss) ...


4

I will give you teh codez because I am shameless: schtasks /create /RU DOMAIN\administrator /RP PASSWORD /SC Once /SD 06/28/2014 /ST 03:00 /TN Reboot /tr "C:\WINDOWS\system32\shutdown -r -t 1 -f" Replace the DOMAIN\Administrator with the appropriate Administrator account and PASSWORD with the appropriate password.


3

Standard advice applies: you seem to be quite out of your depths, thus you should be better off hiring someone who knows what he's doing. That said, you can't directly migrate from Exchange 2003 to Exchange 2013; you need to first perform a full migration to Exchange 2010 and completely remove Exchange 2003 from your organization; then you can migrate to ...


3

A word about security (in response to a comment): software out of maintenance does not get security updates so such operating systems and software stacks must be kept carefully separated with this in mind. Such systems and the services they provide should not be directly accessible to users. This means the answer is different if the servers are performing ...


2

I'd strongly recommend moving away from WMIC.EXE, and use PowerShell instead. PowerShell lets you use RPC to access the remote server's WMI interface, negating the need for PsExec. Although PsExec is a useful tool, I'd only use it if absolutely necessary, as it creates a service on the remote server, the newly created remote service then spawns a process ...


2

The Bypass Traverse Checking user right already gives them the ability to do this. Give them no NTFS permissions on the parent folders. Give them the appropriate NTFS permissions on the subfolders and/or files. They'll be able to traverse the parent folders, without seeing their contents, and get to the subfolders and/or files by accessing them via the ...


1

You're looking at an application managed by Windows Installer. The installation is identified by a globally-unique identifier (GUID, which you are referring to as the "SID"). That GUID is used in the name of registry locations where information about the installation is stored. The difference in the appearance of the GUID in one place versus another is ...


1

You setup another Exchange Server and then migrate the mailboxes. There are tutorials out there. I think you can't directly migrate from 2003 to 2013 tough, and you need to go "through" a 2010 server.


1

The note from Microsoft about all subfolders only applies if you specify just a folder, for example C:\Users. This blocks all executables in all subfolders. But as you correctly noted, if you specify C:\Users*.exe to block only files with extension exe, they are only locked in C:\Users, not for example in C:\Users\Tom. I do not have an answer for this ...


1

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 ...


1

"Win32_Printer" and "net view" are querying different objects. "Win32_Printer" will enumerate all installed printer objects and can be quite slow on print servers. This will expose lots of good data and some management functions. However, you're only interested in the names of queues, so this is probably over-kill for your needs. "net view" on the other ...


1

The most likely cause of this is that you ran the MSI silently via WMI and interactively when logged onto the server (short of the install never having run at all). Is this what you actually did? There are also other reasons that can cause the same problem. We would need to see the content of the update.cmd file to be sure. To deal with the silent versus ...


1

I found a way using robocopy which comes with Windows Server 2003 Resource Kit Tools It has an option that only logs the differences without copying them. The command was: ROBOCOPY C:\Data2\ \\srvbk1\d$\DATA\DATA\ /e /l /log:diff.txt Explanation of the command switches used above: /e Recurse through sub-directories (including empty ones) /l Don’t ...



Only top voted, non community-wiki answers of a minimum length are eligible