We have been working on migrating our WINS server onto a windows 2003 server. After migrating there have been problems.
One of the users claimed that he could not access the shares on some of servers and also could not see all the computers on the network. That meant that his machine is not pointing to the new wins server.
Now, to troubleshoot we had three options. One, that if the wins is locally set up on his laptop. Second, VPN is pushing out wrong wins or third that his laptop is connected to different domain which points to old wins server.
He was asked to run the command prompt and using ipconfig /all while logged in to vpn and find the wins ip adreess. As expected it was pointing to the wrong wins server.
It came out some changes be made on the vpn 3000 concentrator. I used webvpn to make the relevant changes. Under configuration>user management>groups>internal users group>genaral I changed the primary wins address to the new wins server and secondary to the old one.

To confirm it I connected to the vpn and did ipconfig to find the wins getting pointed out to the new ip address.

In view of auditing the ports on the patch panel in the server room I had to audit a list for all the ground ports across the building to ensure easy allocation of ports (network and phone ) in future.

I first noted down all the ports on the patch panel and then manually found the ground port each one is connected to on the patch panel itself. Secondly I would need to go to each ground port and find out if they are active, if not then mark them as inactive in the audit.

We are done with documenting the things to do for preparing for the new corporate signature. The software is now in test period. In the active directory a new group called Signature Test Group has been created and users been added to it for testing it.
The documentation has been kept as simple as possible to make it understandable for non IT departments as well. But still we were flocked with queries straight away by testers. Problems like Why can't I see my signature while composing email? That is because the signatures are added once the user sends the email and it goes to the exchange server where it gets the user credentials from the Global Address List in Active Directory.

To standardize the email signatures for all employees we had configured our exchange server 2003. According to new settings each external email we would a prefix of a company logo and disclaimer.
but before implementing it we would have liked to make everybody aware of it and provide them with sufficient details to edit their present signatures.
I had been working on this and created a document for the same.

Nigel is satisfied with the upgrades done to his desktop to fix the problem with outlook crashing. After discussions with people at Nouvveau ( our CRM team) it was decided to add some patches to the client software for CRM V3.0 provided by Microsoft.
He has now asked me to implement the same patch for his laptop as well. It is still on testing and if every thing goes fine then we would be looking at wider implementation for the department which uses CRM.
I had already received the media for Veritas backup Exec 11d last week but got the serial keys just today. I thought it to be straight forward as it used to be before to activate the product currently running on the trial key. Due to security changes made by Symantec we now had to login to a licensing portal at symantec website and then using unique customer number and order number track the softwares we bought. That was not enough, then I was supposed to create individual license catalogs for all the 6 different serial keys provided. At last the activation product keys are supplied at email address used to login to the portal.