Category Archives: Server

Adding Contacts to O365 with CSV files – KB10392210

KB10392210

Adding Contacts to Office 365 Exchange server

Customer requesting external contact to be added to the Exchange server and Setting up Distrabution groups

Download the Follow File and have the customer fill out the information for the Contacts needing to be added

ContactsCSV

It includes sample data, which you can delete. But don’t delete the first row. It contains all of the properties for the external contacts. Create a row for each contact that you want to import to Exchange Online. Populate as many of the cells as possible. This information will be displayed in the shared address book for each contact.

However, the following parameters are required to create an external contact and must be populated:

•ExternalEmailAddress
•Name
•FirstName
•LastName
•OtherTelephone
•Manage
After the ontact has returned the needed file you can start to setup the new Distribution groups in O365

The Follow is the commands used to log in to the Servers PowerShell interface

$UserCredential = Get-Credential

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection

Import-PSSession $Session

first command will only create the Contact without extended information

Import-Csv .ExternalContacts.csv|%{New-MailContact -Name $_.Name -DisplayName $_.Name -ExternalEmailAddress $_.ExternalEmailAddress -FirstName $_.FirstName -LastName $_.LastName}

They command will update the Contacts on the system with the extended information

$Contacts = Import-CSV .externalcontacts.csv

$contacts | ForEach {Set-Contact $_.Name -StreetAddress $_.StreetAddress -City $_.City -StateorProvince $_.StateorProvince -PostalCode $_.PostalCode -Phone $_.Phone -MobilePhone $_.MobilePhone -Pager $_.Pager -HomePhone $_.HomePhone -Company $_.Company -Title $_.Title -OtherTelephone $_.OtherTelephone -Department $_.Department -Fax $_.Fax -Initials $_.Initials -Notes $_.Notes -Office $_.Office -Manager $_.Manager}

Used to add the new contacts to the Distribution lists

you will need to remove all but the users names from the CSV file and rename the Tab to Members

Import-CSV <path> | ForEach {Add-DistributionGroupMember -Identity <Distribution Group Name> -Member $_.members}

 

Server / desktop time off

If you get a call about server or desktop time being off there are a few ways to fix it. Either manually reset the time or run a script.

Net Stop W32Time

W32tm /config /syncfromflags:manual /manualpeerlist:0.pool.ntp.org,1.pool.ntp.org,2.pool.ntp.org,3.pool.ntp.org

W32tm /config /reliable:yes

Net Start W32Time

W32tm /config /update

W32tm /resync

 

script explanation:

 

Net Stop W32Time  stop the time service 

W32tm /config /syncfromflags:manual /manualpeerlist:0.pool.ntp.org,1.pool.ntp.org,2.pool.ntp.org,3.pool.ntp.org set the time service to look at the National Time Pool ( external source ) 

W32tm /config /reliable:yes  set time as reliable 

Net Start W32Time   start the time service 

W32tm /config /update   poll the server for the current time 

W32tm /resync  to be run on desktops instead of rebooting to force it to look at the server 

Log File is Damaged – KB10392001

KB10392001

Description:  Received an alert that a log file is damaged for exchange

Windows Event Log: Application
Windows Event Source: ESE
Windows Event ID: 440
Windows Event Severity: Error
Windows Event Message: eseutil (10056) JetDBUtilities – 11056: The log file C:Program FilesMicrosoftExchange ServerV14MailboxMailbox Database 1013801047E00.log is damaged, invalid, or inaccessible (error -501) and cannot be used. If this log file is required for recovery, a good copy of the log file will be needed for recovery to complete successfully.

Steps to resolve: There isn’t much to do about this alert. If it’s important and they need it, you will have to restore the file from a good backup copy.

If this happens a lot, use the troubleshooting and diagnostic tools on the exchange database to check the health of it.

 

How to create a Symantec AV installer KB10391964

How to make an installer to install Symantec AV when remote push fails.

Open the Symantec Console and login

Click “Home” then select “Install protection client to computers”  

 

1

 

Select “New Package Deployment” then “Next”

 

2

 

Accept the defaults on this page

 

3

 

Make sure to select “Save Package” then hit “next”

 

4

 

Specify the output location and hit “Next” and wait 

5

 

6

The blue bar will fill up, it takes 10 to 45 min, and it will tell you its done. Hit finish when you see the window below.

 

7

Please be sure to place the file in a share for IT use or on the desktop of the server. Label it correctly as well.

Transfer the installer to the client pc and install.

 

-finished-

 

Exchange Average Delivery Time – KB10391837

KB10391837

Description:  Received an alert that the customer’s email is taking a long time to get to them

Common customer description: My mail is taking a long time to send or receive

Probing questions: Is this a common issue?

Is this a recent thing that has been happening?

Is there a lot of people using mail?

Steps to isolate: Send test email to yourself

Check inbound/outbound queues

Steps to resolve:

1. Check the alert, see how long it says the time that it’s taking to deliver

2. Log onto the Customer’s OWA with IE, Chrome, or Firefox on your computer or connect to the server and log onto the OWA from there

3. Send a test email to yourself (your email address)

4. See how long it takes before you receive that email

5. You can also run some diagnostics to see if everything is okay

Additional considerations: This could be an issue with the Exchange database or some setting with Exchange.

How to check Trend Micro Seats/Licensing – KB10391778

KB10391778

How to check Trend Micro Cloud Seats

We need the website credentials to enter in here   https://tm.login.trendmicro.com

2

Un check the “Remember Me” box before hitting the Sign button

3

 

Click the “Open console” button

4

 

Click the “License Status” drop down button

5

Here you will see the “Seats Purchased” and “Seats In Use

You will also see next to the word “License Status” a color indicating the status. It works just like a traffic light.

If the status is anything but green or “Seats Purchased” has a smaller number than “Seats In Use” they may need more seats

If the “License Status” is red you will not be able to activate Trend

How to check Trend Micro Server Seats

Log in to the server.

Click “Start” “All Programs” “Trend Micro Worry-Free Business Security Server” “Worry-Free Business Security

1

You will get this page in a web browser

2

Go ahead and click “Continue to this website (not recommended)

Which brings you here where you can enter the password (usually the number 1 or the word ‘trend’ )

3

After you login go to Preferences Product Licenses

4

 

Click on “Product License

5

 

Here you will see the status, usage and expiration

You will also see a button with a color indicating the status. It works just like a traffic light.

If the status is anything but green or the text indicates a over usage of seats they may need to purchase more seats.

If the button is red you will not be able to activate Trend

NTFS Errors: Event ID 55 – KB10391728

Description:  Found NTFS errors in the Event Viewer while performing maintenance

NTFS errors are caused by one of the two things: The disk might have bad sectors or I/O requests issued by the file system to the disk subsystem might not have been completed successfully

Common customer description: Computer seems slow or is telling me that it’s corrupted

Probing questions: Is this a recent occurrence?

Steps to isolate: Check Event Viewer for Event ID 55

Determine which drive the issue is located on

Steps to resolve:

1. Open the Command Prompt as Administrator

2. Run chkntfs on the bad drive

  • chkntfs checks the file system to see if there are any “dirty” bits
  • If the status come back “[Drive] is dirty” or even “[Drive] is clean, go to step 3

3. Run the read-only chkdsk (chkdsk [Drive Letter:]) to make sure in fact that the drive is having an issue

  • chkdsk verifies the file system integrity of a volume and fixes logical file system errors
  • If the chkdsk (drive Letter) comes back with an error, run the chkdsk /f command

4. Call the customer to see when we can reboot their server so the chkdsk can run

5. After the reboot happens, watch the Event Viewer for a couple of days to see if the Event ID 55 comes back.

  • If it doesn’t, you can close the ticket
  • If it does, try running the command chkdsk /r

6. Open command prompt as administrator

7. Run the command chkdsk /r

  • What that does is it locates bad sectors and recovers readable information by checking the entire disk surface for bad sectors and attempt to repair or work around any that it finds, if it can

8. Again you might need to reboot the computer again

9. Repeat Step 7 and watch to see if the NTFS errors come back

 

Exchange 2007/2010 change max send and receive size – KB10391742

You can modify the organizational message size limits using the Set-TransportConfig cmdlet from the Exchange shell:

Set-TransportConfig -MaxReceiveSize 40MB -MaxSendSize 40MB

In Exchange 2007 SP1 and later, you can also set the organizational message size limits using the EMC by going to Organization Configuration | Hub Transport | Global Settings tab | Transport Settings | properties | General tab.

1
Figure 1: Setting the organizational message size limits from the Global Settings tab in the EMC in Exchange 2007 SP1 and later

– Receive Connector limit

To modify the maximum message size on a Receive Connector using the Exchange console, select Server Configuration | Hub Transport | select a Hub Transport server | Receive Connectors -> select a connector | Properties | General tab.

1
Figure 2: Setting the maximum message size on a Receive Connector

To set ReceiveConnector limit using the shell:

Set-ReceiveConnector “CONNECTOR NAME” -MaxMessageSize 40Mb

 

– Send Connector limit

To modify the maximum message size on Send Connectors, select Organization Configuration | Hub Transport | Send Connectors -> select connector | Properties |General tab.

1
Figure 3: Setting the maximum message size on a Send Connector

To set SendConnector limit using the shell:

Set-SendConnector “CONNECTOR NAME” -MaxMessageSize 40Mb

KB10391742

Scan To Email – Exchange With TLS Authentication KB10391615

KB10391615

Create a new Active Directory account With a Mailbox (Example Scanner@domain.com).

Set Password to not expire.

Open up Exchange Management Console.

Create New Receive Connector With the following settings:

Enter the IP address of the scanner (In this example 192.168.41.155).

rc1

rc2

rc3

rc4

 

Log into Scanner / multi-function device.

scanner

 

Navigate to the email or SMTP settings.

Enter IP of exchange server

Port 25

Use TLS / SSL

Enable SMTP authentication

Enter email address

Enter user account

Enter Password

 

Removing Phone from Exchange / Trust Relationship – KB10391463

KB10391463

Description of Work
How to disable a Phone in Office 365 or Exchange 2007 / 2010 when you are disabling a user from accessing their company email

– Option to preform a remote wipe of the Exchange data on the phone

Steps to remove the trust Relationship that Exchange created with the phone

Estimated Time to Complete
Half Hour

Requirements before beginning Service Work
Which user account to disable phone on, Approval from Main contact, Access to Domain Controller

 

Exchange 2013 or Office 365

Logged into the admin account for the company

locate the user in Exchange management that the changes need to be made on

then Double click to open the properties windows noted below

photo3
Next select the “Edit Exchange Properties option

Photo2

On this screen select the

– Disable Exchange ActiveSync

– Disable OWA for Devices

Select the “View Details” Option

phone1

This screen will allow you to

– Remove trust relationships from phones

– preform a remote wipe of the device ” Clear all Exchange Information on the phone ”

when on this screen

– first wipe and devices that need to be clear of exchange data “only if customer requests remote wipe of device

– then remove all devices from the mobile devices list

Exchange 2007 / 2010

open the Exchange Management console on the server hosting exchange

Phone4
select the user and right click on the name

in the drop down menu select “Manage Mobile User”

– if this option is not in the list the user has never paired a mobile device to the account and you can disregard the information

If the option is listed select the item

phone5

From this screen you can wipe a device

– select the device a from the list at the top

– select ‘Preform a remote wipe to clear the mobile phone data” – Only if the Company requests this to be done on the phone

select remove

– to remove partnership from the Exchange to phone select the phone from the list and ” remove mobile phone partnership” then select the remove button

remove all device from the exchange list. this will prevent any phone from accessing the Exchange server

with Exchange 2007 and 2010 a restart of IIS is needed

open a admin command prompt

and run command ” iisreset /noforce ”

this will restart the IIS services on the server and finish the removal of the partnerships on the phone

After Mobile devices are Disabled see article on how to Disable user in AD

http://www.cpumd.com/KB103983