Tag Archives: Server 2012

Force Update the Global Address List Exchange 2007 / 2010 KB10391439

WHEN WILL YOU USE THIS ARTICLE
1. Outlook Address List not showing newly created users or contacts
2. Users not receiving latest contacts in cached mode

 OPEN EXCHANGE MANAGEMENT CONSOLE (EMC) BY DOING THE FOLLOWING:

1. Connect to your Exchange Server using RDP or any remote application
2. Now click on start and type Exchange Ma
3. And select Exchange Management Console from the list
Open EMC
NOW WE WILL START THE UPDATE PROCESS, PLEASE DO THE FOLLOWING:
1. Now Expand Microsoft Exchange > Microsoft Exchange On-Premises > Organization Configuration > Mailbox
Expand EMC2. Now Select the Offline Address Book tab
3. Locate your Default Offline Address book and Right Click on it then select Update. You can also click on the Update link located in the Action pane on the far right after highlighting the Default Global Address List.
Update GAL4. You will receive the following message, just select Yes
Update Warning

5. Now to force the update
6. Open a Admin Command Prompt
7. Type  net stop MSExchangeFDS
8. Type  net start MSExchangeFDS

Done after verification

 

Windows Server 2012 Windows Update Issue – KB10391119

KB10391119

Description:  Windows Server 2012 rebooting at random times after installing updates for maintenance

Steps to resolve:

1. When you are done performing maintenance on the server, log off the server and log back on the server with the administrator credentials

2. Go to Windows Updates

3. On the Windows Updates page, go to change settings

settings

4. Then on the drop down menu, select Never Check for Updates

never check

5. Click Apply and then Ok

**If the settings are grayed out, most likely they have a Group Policy in place. If that’s the case, we do not make any changes to the Group Policy. Leave the service on automatic and log out of the server when you are done.

Additional considerations: We cannot guarantee that the server won’t reboot later that day after you install updates but the fix will not let the server check for updates until we go in and check for it ourselves.

Moving or Re-Sizing Pagefile.sys – KB1039916

KB1039916

Description:  Moving or re-sizing the pagefile because it’s taking up too much space on the drive

Common customer description: I received a call about something about a pagefile…?

Probing questions: Do you remember who contacted you about this?

Do you remember a ticket number?

Steps to isolate: Check previous tickets for low disk space

Steps to resolve:

To get to the screen to change the pagefile

  • For Server 2003

1. Click Start>>Right click Computer>>Click Properties

2. Click the Advanced Tab>>Under performance section click on Setting

3. Click the Advanced Tab>>Under Virtual Memory section click on Change

  • For Server 2008/2011/2012

1. Click Start>>Right click Computer>>Click Properties

2. In left pane, click Advanced System Settings

3. Click on Advanced tab, under Performance, Click Settings

4. Click the advanced tab, under Virtual memory, click Change

5. Clear the Automatically manage paging file size for all drives checkbox

 

Re-sizing Pagefile

Now if the pagefile.sys is just too big or too small, follow the size chart that is above to add or shrink the pagefile to the correct size.

  • The initial size is the current amount of ram installed and the maximum size is the initial size times 1.5 (Ex. 4096 x 1.5 = 6144)
  • After you completed this, the server will require a reboot, call the customer to schedule a reboot of their server.
  • If this cannot be re-sized, move the pagefile.sys to a different drive and follow the steps below

 

Moving Pagefile

1.  Pagefile should be on C:, click on No Paging File then press Set

2. It will say that the system won’t be able to make logs and etc…just click ok

3. Click on the Drive you want to move the pagefile to (D,E,F)

4. Select the Custom Size

  • Remember, the initial size should be the amount of Ram that is installed on the server

1 GB = 1024

2 GB = 2048

3 GB = 3072

4 GB = 4096

6 GB = 6144

8 GB = 8192

12 GB = 12288

16 GB = 16384

24 GB = 24576

28 GB = 28000

32 GB = 32000

  • Maximum Size is the initial size times 1.5 (Ex. 4096 x 1.5 = 6144)

5. Click Set and click OK then click Apply and finally click OK, it will prompt you to restart the computer – DON’T. Reboot the server at the customer’s requested time and date that they prefer

 

Additional considerations: Don’t forget to call the customer for reboot approval, you can not reboot the server without their permission.

Unexpected Shutdown (Previous Shutdown was Unexpected) – KB1039488

KB1039488

Description:  Customer’s Server shut down unexpectedly

Common customer description: The server just shut down randomly

Probing questions: Did you hard shutoff the server?

Was there a recent power outage?

Was a cord unplugged by accident?

Steps to isolate: There only two things you can do: look at Event Viewer (you’ll find these events) and call the customer

previous

kernel

Steps to resolve:

1. Check system up time, this will help pin point the time when the server was shut off

  • Go to Start>>Run>>cmd

cmd

  • Type systeminfo |more

cmd1

  • Check “System Boot Time” in 2008 and higher, “System Uptime” in 2003

cmd2

or

  • Right click on the task bar and click on Task Manager
  • Go to the Performance Tab, it will say “Up Time” (Only 2008, 2011 and 2012 servers. Server 2003 cannot do this task)

task

2. Check Event Viewer to see if there are any events leading up to the shutdown

  • Failed/failing hard drive(s)
  • User32 warnings (indicating that someone or an application had to shut the server down)
  • Temperature issues
  • Microsoft EULA License issues

3. Check to see if there were any server down tickets or someone working on the server (Helpdesk, Tier 2, Onsite Tech)

4. Check HP System Management or Dell Server Administrator to see if there are any failures or warnings

5. Call customer to explain that there was an unexpected shutdown. Find out if they know why

  • Did you have to hard reboot the server?
  • Was there a recent power outage?
  • Was a cord unplugged by accident?

Find out anything you can about why the server was down

Additional considerations: If they don’t know why the server shutdown – see if we could send an onsite out to look over their server to make sure that everything is okay (troubleshoot further)

Low Disk Space Alerts – KB1039460

KB1039460

Description:  Low disk space on the C:, D:, E: etc…

Common customer description: Server receiving a low disk space alert

Exchange running slow

Probing questions: Is this a re-occurring issue that will require on onsite?

Steps to isolate: Check the drives on Computer

Steps to resolve: 

Remember to uninstall any application you install!

Quick Things to Clear Up on the C Drive

1. C:InetpublogfilesLogs

  • Delete files inside the folders up to the last 2 weeks

2.  C:WindowsSoftwareDistributiondownload

  • Remove all folders and files up to the last 2 weeks

3. C:WindowsSystem32logfiles

  • Delete the files inside the folders up to the last 2 weeks

4. WSUS – C:WSUSWsusContent

  • Remove everything up to 1 week old

If WSUS is still big (most likely the database) use the WSUS Server Cleanup Wizard

  • Go to Start>>Administrative Tools>>Windows Server Update Services
    • On the left pane, click the “+” by the server name and click on options
    • On the center pane, click on Server Cleanup Wizard
    • Keep all the check boxes checked and press OK
      • If there is a lot for it to clean – the longer it takes

5. Symantec Virus Definitions (Check to see which version of EndPoint Protection that they have)

  • Delete definitions in the definitions folder up to the last 2 weeks

11.x and 12.0.x

  • Server 2003 – C:Program FilesCommon FilesSymantec SharedVirusDefs
  • Server 2008/2011/2012 – C:ProgramDataSymantecDefinitions

12.1.x

  • Server 2003 – C:Documents and SettingsAll UsersApplication DataSymantecSymantec Endpoint ProtectionCurrentVersionDataDefinitions
  • Server 2008/2011/2012 – C:ProgramDataSymantecSymantec Endpoint ProtectionCurrentVersionDataDefinitions

Refer to article: http://www.symantec.com/business/support/index?page=content&id=TECH141811

6. Use CCleaner and Tree size

  • On the server, go to the run button on the start menu and type OM-CT
    • Go on the DATA (D: ) drive>>TechAdvantage>>Tools>>Tech Utils
      • CCleaner should be there and for Tree Size go to the folder called Tree Size

7. Move or re-size pagefile.sys — refer to article KB1039916

 

***Server 2003 only for these***

1. Delete log files in C:Windows

  • Kb*.log
  • Setup*.log
  • Setup*.old
  • Set*.tmp
    • Delete all files until up to the last 2 weeks

2. C:Windows$NtUninstallKB number$

  • You can delete the folders up to the last 2 weeks

3. C:Windows$ServicePack$

  • You can delete the folders up to the last 2 weeks

4. Disk Cleanup tool

  • Click Start>>All Programs>>Accessories>>System Tools>>Disk Cleanup
  • When using this, you do not want to compress files – Leave that box unchecked

 

What if the space is for a drive other than C:?

  • Try to clear what you can
    • Sometimes it will be hard due to the drive being for their company files, SQL Backups, Backups, or QuickBooks.
  • Drives that have SQL, Backups, or QuickBooks are usually tricky and should be looked at with a Tier 2 tech to determine the proper course of action.
  • If it’s a virtual server, we can simply extend the partition but we need billable approval from the customer to do that.

Also contact the customer if:

  • Company’s Data (Documents/User Data/Applications) is majority of the drive
    • Would they like us to go over it and delete things?
    • Would they take care of it and clean/move things themselves?
    • Would they like an onsite to look into it?
    • Would they like a quote for a new drive?

Contact the AM if:

    • No other options are available other than to replace the drive with a new larger drive
    • If you cleaned all you can on a 2003 server with 10 or 12 GB of disk space, contact the AM to see if the customer would like to get a new drive or a new server – let them work out the details. If you get the alert again and it seems like the customer and the AM haven’t gotten anywhere – talk to Trevor about it.

Additional considerations: Ask the Remote Maintenance Lead or Tier 2 tech for further help. If you are unable to clear up any more space, you will have to contact the customer and/or the AM about this issue. Normally, you will have to contact the customer first about this issue then the AM. Refer to this KB article: KB1039467

A possible onsite might be needed depending on the situation. Make sure you have approval from the appropriate people before escalating.