Restart Windows Internal Database

NET STOP MSSQL$MICROSOFT##SSEE
NET START MSSQL$MICROSOFT##SSEE

Message Tracking in Exchange 2010 Using PowerShell

Get-MessageTrackingLog -Server Mailbox01 -Start "03/13/2013 09:00:00" -End "03/15/2013 17:00:00" -Sender "john@contoso.com"

$Temp = Search-MessageTrackingReport -Identity "David Jones" -Recipients "wendy@contoso.com"

$Temp | %{ Get-MessageTrackingReport -Identity $_.MessageTrackingReportId -BypassDelegateChecking }

http://www.mikepfeiffer.net/2012/01/generating-delivery-reports-and-tracking-messages-from-powershell/ 

This method is disabled by 'moref=vm-ID'

If you get this message when you are trying to Storage Vmotion a VM then this is likely to be a lock in vCentre SQL database for this VM, mostly put in place by the backup system e.g. Netbackup, Veeam etc

Vmware KB 2008957 has all the step to resolve the issue but I found that restarting SQL services is not really required. Carryout all the steps from 1 - 6 and then rerun that backup (incremental is good enough) and then do Storage Vmotion again...

1. Stop the vCenter Services.
2. Take a backup of the vCenter Server database.
3. Run this command against the vCenter Server database.
   
   select * from VPX_VM WHERE FILE_NAME LIKE '%Virtual-Machine-Name%'
   
4. Take note of the numerical ID value returned by the SQL statement in step 3, as this will be required in the SQL statement in steps 5 and 6.
   
5. To confirm the stale entry, run this command against the vCenter Server database:
   
   select * from VPX_DISABLED_METHODS WHERE ENTITY_MO_ID_VAL = 'vm-ID from step 4'
   
6. To remove the stale entry run this command against the vCenter Server database:
   
   delete from VPX_DISABLED_METHODS WHERE ENTITY_MO_ID_VAL = 'vm-ID from step 4'

ESXi 5.1 not detecting HBA adapter

Steps:

1) Make sure HBA is connected on the PCI slot and visible under esx hardware list:

esxcli hardware pci list

2) Check if VMKernel can detect any storage via Fibre Channel

esxcli storage san fc list
 
(output will be blank line if HBA driver is missing but HBA appears to be in PCI card determined from step 1)
esxcli storage core adapter rescan

3) Search and download the relevant ESXi drivers for HBA

the recommended driver (bfa) version for 82B in ESXi 5.1 is 3.0.0.0
You can download it from the following URL.
https://my.vmware.com/web/vmware/details?downloadGroup=DT-ESXi50-BROCADE-bfa-3000&productId=229

4) Download the driver and install it using following instructions:

New Installation
----------------

For new installs, you should perform the following steps:

    1. Copy the VIB to the ESX server.  Technically, you can
           place the file anywhere that is accessible to the ESX console shell,
           but for these instructions, we'll assume the location is in '/tmp'.

           Here's an example of using the Linux 'scp' utility to copy the file
           from a local system to an ESX server located at 10.10.10.10:
             scp VMware_bootbank_net-driver.1.1.0-1vmw.0.0.372183.vib root@10.10.10.10:/tmp

    2. Issue the following command (full path to the VIB must be specified):
              esxcli software vib install -v {VIBFILE}
      
           In the example above, this would be:
              esxcli software vib install -v /tmp/VMware_bootbank_net-driver.1.1.0-1vmw.0.0.372183.vib

Note: Depending on the certificate used to sign the VIB, you may need to
      change the host acceptance level.  To do this, use the following command:
        esxcli software acceptance set --level=<level>
      Also, depending on the type of VIB being installed, you may have to put
      ESX into maintenance mode.  This can be done through the VI Client, or by
      adding the '--maintenance-mode' option to the above esxcli command.


Upgrade Installation
--------------------

The upgrade process is similar to a new install, except the command that should
be issued is the following:

    esxcli software vib upgrade -v {VIBFILE}
 

ESXi host 4.1 to 5.1 upgrade stuck on 22%

If your ESXi host update from v4.1 to 5.1 stalls, crashes or freezes on 22% don't panic wait for it to finish if no joy then next time don't forget to untick disable DPM box in the upgrade wizard, works for me every time.

When it happened first time, I remotely accessed the host and found esxi host frozen on loading screen (black & yellow) on Power management services.

vCentre Single Sign On Database Connection has failed

When I came across this error
"Databse connection has failed. You can refer to the vm-sso-javaLib.log in the system temporary folder for more information" during the installation of vSphere 5.1 SSO.

I fixed it my changing MS SQL Database authentication from Windows to SQL and Windows mixed authentication.


Godd Luck!!

Power off unresponsive VM

Using the ESXi 5.x esxcli command to power off a virtual machine

The esxcli command can be used locally or remotely to power off a virtual machine running on ESXi 5.x. For more information, see the esxcli vm Commands section of the vSphere Command-Line Interface Reference.

1. Open a console session where the esxcli tool is available, either in the ESXi Shell, the vSphere Management Assistant (vMA), or the location where the vSphere Command-Line Interface (vCLI) is installed.
   
   
2. Get a list of running virtual machines, identified by World ID, UUID, Display Name, and path to the .vmx configuration file, using this command:
   
   esxcli vm process list
   
   
3. Power off one of the virtual machines from the list using this command:
   
   esxcli vm process kill --type=[soft,hard,force] --world-id=WorldNumber
   
   Notes:
   Three power-off methods are available. Soft is the most graceful, hard performs an immediate shutdown, and force should be used as a last resort.
   Alternate power off command syntax is: esxcli vm process kill -t [soft,hard,force] -w WorldNumber
   
   
4. Repeat Step 2 and validate that the virtual machine is no longer running.

For ESXi 4.1:

1. Get a list of running virtual machines, identified by World ID, UUID, Display Name, and path to the .vmx configuration file, using this command:
   
   esxcli vms vm list
   
   
2. Power off one of the virtual machines from the list using this command:
   
   esxcli vms vm kill --type=[soft,hard,force] --world-id=WorldNumber

Using the ESXi command-line utility vim-cmd to power off the virtual machine

1. On the ESXi console, enter Tech Support mode and log in as root. For more information, see Tech Support Mode for Emergency Support (1003677).
2. Get a list of all registered virtual machines, identified by their VMID, Display Name, and path to the .vmx configuration file, using this command:
   
   vim-cmd vmsvc/getallvms
   
   
3. To get the current state of a virtual machine:
   
   vim-cmd vmsvc/power.getstate VMID
   
   
4. Shutdown the virtual machine using the VMID found in Step 2 and run:
   
   vim-cmd vmsvc/power.shutdown VMID
   
   Note: If the virtual machine fails to shut down, use this command:
   
   vim-cmd vmsvc/power.off VMID
   
   
   
   http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1014165

VMWare vConverter A General System error occurred: unknown internal error

If you come across following error whilst converting Physical machine to Virtual using VMware vCenter Converter Standalone version 5.x use following steps to overcome this message (i found these steps from different forums which seemed to have worked for some people but what worked for me is Step4).



A general system error occurred: unknown internal error.

1. Click Finish again to ignore and complete the P2V
2. From Server TCP/IP settings remove static IP addresses and set dynamic IP detection
3. (Source: VMware vConverter release notes) On ESX hosts earlier than 5.0 and managed by vCenter Server, you cannot submit conversion jobs if the name of the destination datastore contains non-ASCII characters
When you click Finish in the Conversion wizard, the following error message appears: A general system error occurred: unknown internal error. This issue is observed for VMware Infrastructure virtual machine destinations, when you connect to a destination vCenter Server and select a destination datastore that has non-ASCII characters in its name.
Workaround: Connect directly to the destination ESX host instead of the vCenter Server.
4. Download and complete the conversion using vConverter v4.3 (works every time).

Configuring ISCSI port binding on vSphere using CLI

Configuring Port Binding on vSphere 5.0 Using CLI

Run the following commands from the vSphere 5.0 host CLI to bind the VMkernel network adapter to the  iSCSI adapter:

esxcli iscsi networkportal add --nic vmk0 --adapter vmhbaXX

esxcli iscsi networkportal add --nic vmk1 --adapter vmhbaXX

Where vmk0 and vmk1 are the VMkernel network adapters compatible with iSCSI port binding requirements.  You can get the list of VMkernel network adapters connected to  all vSwitches by using  the command   

esxcfg-vmknic –l

vmhbaXX  is the software iSCSI adapter vmhba ID. You can verify the binding details by using the  following command: 

esxcli iscsi networkportal list --adapter vmhbaXX.

Then rescan the software iSCSI adapter to verify that multiple paths are available for iSCSI LUNs.

Configuring Port Binding on vSphere 4.x Using CLI

To enable vmknic-based multipathing for software iSCSI, run the following CLI commands:

esxcli swiscsi nic add --nic vmk0 --adapter vmhbaXX

esxcli swiscsi nic add --nic vmk1 --adapter vmhbaXX

Where  vmk0 and  vmk1 are the VMkernel network adapters  compatible with iSCSI port binding requirements. You can get the list of VMkernel network  adapters connected to all vSwitches by using the command 

esxcfg-vmknic -l.

vmhbaXX is the software iSCSI adapter vmhba ID.  After configuring port binding, you can verify the binding details by using the following command: 

esxcli swiscsi nic list --adapter vmhbaXX. 

Then rescan the software iSCSI adapter to verify that multiple paths are available for iSCSI LUNs.



http://www.vmware.com/files/pdf/techpaper/vmware-multipathing-configuration-software-iSCSI-port-binding.pdf

Unable to find the system volume, reconfiguration is not possible, VMWARE P2V error

Applies to Windows Vista, 7, Server 2008, Server 2008 R2

To resolve this issue:

1. Import the virtual machine to vCenter Server.
2. Boot the virtual machine from the correct Microsoft Windows installation media (Correct architecture and version of the OS).
3. Select the appropriate keyboard layout and language options and click Next.
4. Click Repair your computer.
5. Select the operating system to be repaired and click Next.
6. Click the Command Prompt.
7. Type bcdedit and press Enter.
8. Under the Windows Boot Manager title with the identifier set to {bootmgr}, you may see that the device is set to boot.  Similarly, under the Windows Boot Loader with the identifier set to {default}, you may see that the device and osdevice are set to boot. These items should be set properly for your environment. Usually these appear as partition=C:.  In some cases the {default} identifier may have them set to partition=D:.
   
   Run these commands to correct the configuration:
   
   Note: bcdedit is located in the following path, c:\windows\system32bcdedit /set {bootmgr} device partition=C:
   
   bcdedit /set {default} device partition=C:
   
   bcdedit /set {default} osdevice partition=C:
9. Type exit at the command prompt and select Shutdown.
10. Try to reconfigure using VMware converter. The reconfigure should now complete successfully. If it fails again, repeat Steps 1 to 7 and then run these commands to set the default device to partition=D::
    
    bcdedit /set {bootmgr} device partition=C:
    
    bcdedit /set {default} device partition=D:
    
    bcdedit /set {default} osdevice partition=D:

How to disable firewall command line?

To Disable:
netsh firewall set opmode disable

To Enable:
netsh firewall set opmode enable

How to clear preferred IP address

How to clear preferred IP address?

Step 1. Goto Start, Run, CMD to open a command prompt.
Step 2. Reset WINSOCK entries to installation defaults: netsh winsock reset catalog
Step 3. Reset TCP/IP stack to installation defaults. netsh int ip reset reset.log
Step 4. Reboot the machine.

Disk extended in Computer Management not showing in My Computer

If you come across a Virtual Machine running out of space and you are about to provision more space and extend it make note that extending disk from Computer Management may increase the disk space on Computer Management window but also check from My Computer to ensure disk is actually extended.

If you come across this problem where disks showing in My Computer window are not extending after a refresh then do following:

• Allocate more space to the VM
• run Re-Scan from Disk Management
• use Diskpart to extend as shown in the screenshot below

Uninstall lastest installed Windows Patches

Excellent script, works every time.

-------------------
 
' Script to enumerate last applied hotfixes, and rollback

on error resume next
const forappending = 8
const forwriting=2
const forreading=1
Const dictKey  = 1
Const dictItem = 2

' **********set to 0 to get out of testmode**********
testmode=0
' ***************************************************

Logpath="C:\hotfixundo.log"

Set fso = createObject("Scripting.FileSystemObject")
set windir=fso.GetSpecialFolder(0)
call stamplog("*************************************************************")
call stamplog("Starting process, windows directory is "&windir.path)

lastdate=""
' enumerate subfolders, check date.
    For Each Subfolder in windir.SubFolders
    if instr(lcase(subfolder.name),"$ntuninstall")<>0 then
        if lastdate="" then
            lastdate=subfolder.datecreated
        end if
        if datediff("d",lastdate,subfolder.datecreated)>1 then
            lastdate=subfolder.datecreated
        end if
    end if
    Next

call stamplog("Latest date found for uninstall folder is "&lastdate)
' loop again, creating a list of directories to be targeted.

set list = CreateObject("Scripting.Dictionary")

call stamplog ("Processing the following directories:")
    For Each Subfolder in windir.SubFolders
    if instr(lcase(subfolder.name),"$ntuninstall")<>0 then
        if datediff("d",lastdate,subfolder.datecreated)<1 and datediff("d",lastdate,subfolder.datecreated)>=0 then
            list.add subfolder.datecreated,subfolder.path
            call stamplog2(subfolder.path)
        end if
    end if
    Next

' sort dictionary
sortdictionary list,dictkey

' loop through list, shell out to run spuninst for each directory, last first
for each location in list
call stamplog("Launching "& list.item(location)&"\spuninst\spuninst.exe")
err.clear
if testmode=0 then
run list.item(location)&"\spuninst\spuninst.exe /quiet /passive /norestart"
else
call stamplog("***TESTMODE - Uninstall NOT run***")
end if
next
call stamplog("Finished at "&date&" "&time)

' Stamp line of text to specified logfile
sub stamplog(text)
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objTextFile = objFSO.OpenTextFile _
    (logpath, Forappending, True)
objtextfile.writeline(text)
wscript.echo (text)
objTextFile.Close
end sub

sub stamplog2(text)
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set objTextFile = objFSO.OpenTextFile _
    (logpath, Forappending, True)
objtextfile.writeline(text)
'wscript.echo (text)
objTextFile.Close
end sub


' Run function
Function Run (ByVal cmd)
   Dim sh: Set sh = CreateObject("WScript.Shell")
   Dim wsx: Set wsx = Sh.Exec(cmd)
   If wsx.ProcessID = 0 And wsx.Status = 1 Then
      ' (The Win98 version of VBScript does not detect WshShell.Exec errors)
      Err.Raise vbObjectError,,"WshShell.Exec failed."
      End If
   Do
      Dim Status: Status = wsx.Status
      WScript.StdOut.Write wsx.StdOut.ReadAll()
      WScript.StdErr.Write wsx.StdErr.ReadAll()
      If Status <> 0 Then Exit Do
      WScript.Sleep 10
      Loop
   Run = wsx.ExitCode
   End Function

' Runs an internal command interpreter command.
Function RunCmd (ByVal cmd)
   RunCmd = Run("%ComSpec% /c " & cmd)
   End Function

' Sort function
Function SortDictionary(objDict,intSort)
  ' declare our variables
  Dim strDict()
  Dim objKey
  Dim strKey,strItem
  Dim X,Y,Z

  ' get the dictionary count
  Z = objDict.Count

  ' we need more than one item to warrant sorting
  If Z > 1 Then
    ' create an array to store dictionary information
    ReDim strDict(Z,2)
    X = 0
    ' populate the string array
    For Each objKey In objDict
        strDict(X,dictKey)  = CStr(objKey)
        strDict(X,dictItem) = CStr(objDict(objKey))
        X = X + 1
    Next

    ' perform a a shell sort of the string array
    For X = 0 to (Z - 2)
      For Y = X to (Z - 1)
        If StrComp(strDict(X,intSort),strDict(Y,intSort),vbTextCompare) > 0 Then
            strKey  = strDict(X,dictKey)
            strItem = strDict(X,dictItem)
            strDict(X,dictKey)  = strDict(Y,dictKey)
            strDict(X,dictItem) = strDict(Y,dictItem)
            strDict(Y,dictKey)  = strKey
            strDict(Y,dictItem) = strItem
        End If
      Next
    Next

    ' erase the contents of the dictionary object
    objDict.RemoveAll

    ' repopulate the dictionary with the sorted information
    For x=(z-1) to 0 step -1
'    For X = 0 to (Z - 1)
      objDict.Add strDict(X,dictKey), strDict(X,dictItem)
    Next

  End If

End Function

Migrate Active Directory Home Folder from Windows Server 2003 to 2008

 Copy all the data across to new server using xcopy


log onto the file server where all home folder resides and run:

xcopy souce dectination /I /C /E /Y

(remember ICEY for switches )

 /I           If destination does not exist and copying more than one file,
             assumes that destination must be a directory.
 /C           Continues copying even if errors occur.
 /E           Copies directories and subdirectories, including empty ones.
 /Y           Suppresses prompting to confirm you want to overwrite an



Get usernames of staff on current file server to be migrated from Active Directory Home Folder Path filter

dsquery * dc=testdomain,dc=com -filter "(&(objectCategory=Person)(objectClass=User)(HomeDirectory=\5c\5cFILEServer1\5cHomeFolder\5c*))" -attr samAccountName > report.txt

 (5c tells dsquery that '\' is not part of the command and string instead)

Modify the Active Directory Home Folder Path


create a batch file:



for /f "eol=; tokens=1" %%i in (report.txt) do call :PROCESS %%i

goto :EOF


:PROCESS
set var=%*
 
dsquery * dc=testdomain,dc=com -filter "(&(objectCategory=Person)(objectClass=User)(HomeDirectory=\5c\5cFILEServer1\5cHomeFolder\5c%var%))" | dsmod user -hmdir \\FILEServer2\HomeFolder\%var%\

:Exit

Error while running health check script

Error Message: Configuration Issues – HA agent on host in cluster clustername in datacentre has an error : Error while running health check script.


If you get this error message, follow these steps:

• Unconfigure HA 
• wait for it to finish
• Reconfigure HA

ESXi Host Memory Swapping and Balloon not deflating - Solved

I came across an interesting problem where hypervisor's memory was ballooning although there wasn't a memory contention on the host. 


Problem:

Host has 32GB of RAM and provisioned RAM is 20GB, there was absolutely no reason for Memory swapping or Ballooning but when I did SSH and esxtop then 'm' for memory, you can see in the screenshot memory swapping is taking place:

This was confirmed from the VIClient Performance tab as well where 1.5GB  of hypervisor's memory was in used by Baloon drivers.
I've also added screenshot from VKernel vOPS

After going back to basis and checking esxtop again, I found that although MEMSZ  is 2048MB the GRANT memory is 449.11MB this tells me something is wrong with resource allocation.
On checking VM Properties, strangely there is a limit of 512MB on the memory  resources which is not visible in Summary and you can also see from the screenshot memory limit bar wasn't moved or adjusted to 512MB.

You can also run following command (change the VMNAME) to identify the memory size and maximum memory size

egrep "memsize|sched.mem.max" /vmfs/volumes/*/*/VMNAME.vmx | awk -F/ '{print $6}' | more

Solution:

If sched.mem.max is smaller than memsize, the balloon driver can start consuming memory (especially if the guest operating system application has periodic bursts of memory usage). However, this setting can cause the balloon driver to retain its hold on memory. If the guest operating system requires memory that is made unavailable by the balloon driver, the guest operating system starts using swap memory instead, which slows it down considerably.

To force the balloon driver to release its hold on memory and prevent the guest operating system from using swap space, use one of these options:

• Set the value of sched.mem.max to the allocated memory or greater.
• Select the virtual machine's Resources > Memory > Limit > Unlimited box.
• Migrate the virtual machine to another host.

After completing the VMotion check the performace monitor and see memory release from the Balloon drivers and difference in VM performance and VM memory chart.

Possible Cause:

Migrating a virtual machine from ESX 2.x to 3.x or 4.x may cause a carry-over of memory reservation that is smaller than the virtual machine's allocated memory (likely a customer-specific setting).

Auto delete files older than x number of days

Following script is ideal where you want to clear the space from backup repository and keep files created in last x number of day, I've been utilizing this to delete all SQL backup files *.bak from backup repository D:\foldername where anything older than 6 days should be deleted.

Create a batch file  Script.bat and Add it the Scheduled Tasks to run daily/weekly/monthly


forfiles /p "D:\foldername" /m *.bak /s /d -6 /c "cmd /c del @PATH"


Switches used:

/P    pathname
/M    searchmask
/S   recuse and check all the subdirectories
/D    date
Selects files with a last modified date greater than or equal to (+), or less than or equal to (-), the specified date using the "dd/MM/yyyy" format; or selects files with a last modified date greater than or equal to (+) the current date plus "dd" days, or less than or equal to (-) the current date minus "dd" days. A valid "dd"  number of days can be any number in the range of 0 - 32768. "+" is taken as default sign if not specified.


/C    command       Indicates the command to execute for each file.
                    Command strings should be wrapped in double quotes.

                    The default command is "cmd /c echo @file".

                    The following variables can be used in the command string:

                    @file    - returns the name of the file.
                    @fname   - returns the file name without extension.
                    @ext     - returns only the extension of the file.
                    @path    - returns the full path of the file.
                    @relpath - returns the relative path of the file.
                    @isdir   - returns "TRUE" if a file type is a directory, and "FALSE" for files.
                    @fsize   - returns the size of the file in bytes.
                    @fdate   - returns the last modified date of the file.
                    @ftime   - returns the last modified time of the file.

Internal CMD.exe commands should be preceded with "cmd /c".

Active Directory Health Check Script

netdom query fsmo > C:\temp\HealthCheck_FSMO_roles.txt
Dcdiag.exe /v > c:\temp\HealthCheck_dcdiag.txt
Dcdiag.exe /q > c:\temp\HealthCheck_dcdiag_erroronly.txt
Netdiag.exe /v > c:\temp\HealthCheck_Netdiag.txt
Netsh dhcp show server > c:\temp\HealthCheck_dhcp.txt
Repadmin /showreps > c:\temp\HealthCheck_rep_partners.txt
repadmin /replsum /errorsonly > c:\temp\HealthCheck_rep_erroronly.txt

Consolidate Helper- 0

If you are using VSphere 4.x or higher and Veeam Backup & Replication v6 and getting random 'Consolidate Helper- 0' snapshot(s) in snapshot manager, as shown in the screenshot, it is time to upgrade to Veaam Backup & Replication version 6.5. For whatever reason you cannot upgrade to 6.5 or downgrade to 5 then create an alert in VIClietnt Alarms to notify VMs running on snapshot and delete the snapshot manually as soon as you get an alert.

Having couple or more of these Snapshot will massively deteriorate your VMs performance specially if this is on your File, SQL or Exchange server which require high disk read and write IOs. Also not to forget the disk space they consume which carry great risk of bringing your VM(s) to a complete halt and the time it takes to delete them to bring your VMs up and online.

Easy Out Of Office for Exchange 2003, 2007, 2010

http://sourceforge.net/projects/bulkoutofoffice/files/BulkOoO-v4.zip/download

Bulk Out of Office Assistant for Exchange Admins

Download link:
http://sourceforge.net/projects/bulkoutofoffice/files/BulkOoO-v4.zip/download
Name: 

Bulk Out Of Office For Exchange 2003 2007 2010 Admins
Description: 

• Handy tool for Ms Exchange Admins that allow:
  

Setup out of office message with just few clicks - No need to 'owa' user's mailbox to setup an Out of Office Message
Create bulk out of office message using a CSV file
Application detects Exchange Servers Names and populate Server Name box for you to select.
Progress bar updates keeps you updated when modifying OoO in bulk
Works on Windows XP, 7, Server 2003, 2008 (Ms Outlook required, see requirement section below)


Requirements:


Microsoft Exchange MAPI Client  (Ms Outlook) 
Microsoft Download Collaboration Data Objects CDO 1.2.1 or higher 

(Not required if you are running BulkOutOfOffice from Exchange Server)



For Outlook 2003 – Enable CDO from Add and Remove Programs

http://j-integra.intrinsyc.com/support/kb/article.aspx?id=113792

For Outlook 2007 – download and install from here

http://www.microsoft.com/en-gb/download/details.aspx?id=3671

For Outlook 2010 – CDO is not provided by Microsoft

Workaround is to uninstall MS Outlook 2010, install CDO and then reinstall MS Outlook 2010


And of course Windows XP, 7, Sever 2003, 2008 

Files:
BulkOoO-v4.exe
gradient-background.jpg
microsoft_office_outlook.ico
microsoft_office_outlook.png 
ExchangeCdo.MSI for Outlook 2007

Sample.csv –(missed during compilation, will be updated soon)

Example of Sample.csv





 


  

  

Mail Server Name

  

  

Mailbox Name or Email Address

  

  

Out Of Office Message

  

  

Enable/Disable

 

  

  

ExchServer1

  

  

testuser1@domain.com

  

  

This Mailbox is no longer monitored
  resend you email to newaddress1@domain.com

  

  

TRUE

 

  

  

ExchServer2

  

  

testuser2

  

  

This Mailbox is no longer monitored
  resend you email to newaddress2@domain.com

  

  

FALSE

 

  

  

MailServer

  

  

xyzuser

  

  

This Mailbox is no longer monitored
  resend you email to newaddress3@domain.com

  

  

TRUE

 

 
Problems:

Bulk Out of Office will freeze if :

Your PC is member of a workgroup
Cannot communicate with the AD and Exchange Servers in your organisation