Something I have frequently seen implemented incorrectly on Windows Server domains is time synchronization. Many admins think that by creating a GPO with a modified policy setting for 'Configure Windows NTP Client' (and using it to address an NTP source) all Servers and Clients will synchronize their time with that source. This isn't entirely true and there is actually a time hierarchy that should be considered when implementing time synchronization for each domain.
I had a problem the other day when I went to logon to a server using RDP and the text fields where you enter your username and password were black! I typed in my credentials anyway and found that I could still logon to the server. After this there seemed to be no other issues.
I am frequently asked to allow access to our servers for 3rd party company usually trying to fix some sort of software issue in their application (the typical scenario.) Most companies tend to use applications such as GoToMeeting or Live Meeting which I’ve never really been in favour of. Recently I was told that in order for a new implementation to commence I would have to give a company VPN access to our network and Remote Desktop Connections onto the relevant servers.
As part of my Service Level Agreement at work I have to produce a monthly uptime report for each server. Rather than generate individual reports for each server I decided to write a KiXtart script that would generate a report for all servers and email it to me each month.
At work there is an old web application that is managed offsite by a hosting company. It runs on Oracle 9iAS. Apparently there is an issue with Oracle 9i and the web service will frequently crash (due to a known caching problem) taking the application offline.
I was recently asked to investigate a problem with a server and the lack of space on a partition. After a quick look using Treesize I noticed a suspicious folder being used by an application for logging purposes.
A common problem I have encountered when using the legacy Remote Installation Services (RIS) to install operating system(s) onto new computers, is caused by the size of the hard disk that you wish to install the operating system onto.
After its recent release I installed Service Pack 2 on all computers running Microsoft Windows Server 2003 at work. I encountered a few strange problems.