Those Little Everyday IT Issues

The default self-sign certificate that comes with the Exchange 2007 was deleted after installing a new certificate from Verisign. But as luck would have it, the name of our company got changed and for compliance purpose, we had to change the certificate so that the new company name is projected. It took almost two weeks for the new certificate to come. But in the meantime we had to use a certificate (a self-sign one at the least) as Exchange 2007 cannot run without a certificate we had already deleted the self sign cert that comes by default. The steps below will tell you the ways that I have taken to fix it. After many trial and errors, the self-sign certificate is working now. I cannot guarantee that information given below will perfectly work for you. { Continue at your own risk } Open Exchange Management Shell (EMS) and type the command as shown below to generate the Certificate Signing Request (CSR) [PS] C:\Documents and Settings\Administrator>New-ExchangeCertificate ...

Exchange Server 2007 was installed on a Windows Server 2003 R2 Standard Edition whose C drive has a disk size of ~30 GB. In less than two years time, the free space available on C drive is less than 2 GB. {High Alert! High Alert!}. First thing after a bit of googling was to see where the Exchange logs are being written. Unfortunately, Exchange logs are being written on a separate drive. So now, further googling needs to be done on what is eating up the spaces on the C drive. We had Enterprise Vault 2007 (EV) as an email archiving tool. EV for Outlook Web Access writes some kind of logs in "C:\Program Files\Enterprise Vault\OWA 2007\logs" and that thing is eating up almost 10GB of space. So i had to transfer the logs and any new logs need to be written to a new location on a separate drive to free up the space. The steps take to do so are as follows: Within the IIS Manager right-click on the OWA virtual directory and select properties Select the ASP.NET tab Then choose ...

To back up a mailbox as PSTs, it is very important to grant the full permission first for that mailbox to the user accessing the console. The two commands are listed below: Add-mailboxpermission -identity -accessrights fullaccess -user export-mailbox -Identity -PSTFolderPath One important note is that the command cannot be run from a 64bit environment and hence the EMC and EMS must be downloaded and run from a 32 bit windows OS.

Verify that your terminal, laptop, or terminal server is operational. Configure that terminal device or the terminal emulation software to use the following settings: * 8N1: eight data bits, no parity, one stop bit * 9600 baud * Disable hardware flow control (CTS/RTS) Connect a serial cable from the serial port on the server's back panel to a terminal device. Refer to your -specific documentation or the supplement for the location of the serial port. When the system has booted, the ILOM displays its login prompt: SUNSPnnnnnnnnnn login: The first string in the prompt is the default host name. It consists of the prefix SUNSP and the ILOM's MAC address. The MAC address for each ILOM is unique. Log in to the CLI: Type the default user name, root. Type the default password, changeme. Once you have successfully logged in, the ILOM displays the ILOM default command prompt: -> The ILOM is now accessing the CLI. You can now run CL...

Neither 'am an expert in IT matters nor my writings will make any sense to the IT Pros. It was sheer luck and the tenacious effort that I have put in that I was able to come out with something regarding this vulnerability. Most likely the network got infected by some trojan due to the above mentioned vulnerability. Two major outcomes (that i faced) were LOSS IN NETWORK SERVICES & ANTI VIRUS GETS DISABLED. This haunted me for almost a week and I am not saying that the steps below can clean the infection, but it did help me in bringing up the services again. The steps are: 1. Add a DWORD Value (Smb2; Value=0) in HKEY_LOCAL_MACHINE\System\ CurrentControlSet\Services \LanmanServer\Parameters 2. Restart "Server" from services 3. Run the command (without the quotes) as administrator "netsh winsock reset". After this command one will need to restart the system. Once it boots up, you should be able to see your Network Connections or Anti Virus getting enab...