After upgrading our ShoreTel 11.1 system to the latest version, 12.1, the sites with Voice series switches no longer had voice mail capabilities. If you missed a call the link would just ring 4 times and go to dead air.

Knowing that V series ShoreGear switches were sensitive to NTP for voice mail to function, it was time to check the switch configuration.

When connecting via SSH using admin/ShoreTel as my login/password, I noticed the configuration showed the following incorrect NTP info:

Time server IP address = 132.163.4.101

However, when I tried to change the time server IP I received this message:

please use Director’s Sites page to set Time Server (NTP) Ip Address

Logging into Director’s Sites page and inputting the Network Time Protocol Server and rebooting the switch did the trick.

ShoreWare Director > Administration > Sites > My specific site:

Required: Cisco ASA running software version 8.2.2 or later
Cisco Documentation

CLI Configuration:

ciscoasa# configure terminal
ciscoasa(config)# policy-map type inspect dns preset_dns_map
ciscoasa(config-pmap)# parameters
ciscoasa(config-pmap-p)# message-length maximum client auto
ciscoasa(config-pmap-p)# write memory

You can now exit your SSH connection.

ciscoasa# show running-config

You should see this somewhere in your configuration now:

!
policy-map type inspect dns preset_dns_map
parameters
message-length maximum client auto
message-length maximum 512
policy-map global-policy
class global-class
inspect ftp
inspect icmp
inspect dns preset_dns_map
!

Note: The message-length maximum 512 should already be there from the inspection defaults.

ASDM Configuration:

Once the XenServer Ubuntu VM rebooted, I was no longer able to boot and just received a BusyBox initramfs prompt.

Grub2 is supposed to allow you to hold Shift to get to the grub menu but this did not work at all for me. Just kept seeing a blank screen and eventually the initramfs screen. I think this is a XenServer limitation, as I was trying from the VM console.

The version of grub2 is 1.99 beginning with Ubuntu 11.04 and we can boot with the LiveCD to ChRoot and remove the wrong kernel. Older versions should work too, but I am just letting you know what I was facing.

Boot the appropriate Ubuntu LiveCD (needs to be the exact same bit/version of your installed OS).

Next, mount your disk assuming your /boot partition is not on a separate partition:

sudo mount /dev/sda1 /mnt
for i in /dev /dev/pts /proc /sys; do sudo mount -B $i /mnt$i; done
sudo chroot /mnt

Once ChRooted run apt-get remove linux-image-<your-version-to-remove> (review boot/grub/grub.cfg to see what the version is you want to remove: vmlinuz-2.6.32-13-virtual):

apt-get remove linux-image-2.6.38-13-virtual
exit chroot by pressing CTRL-D
for i in /sys /proc /dev/pts /dev; do sudo umount /mnt$i; done
sudo umount /mnt
sudo reboot

For further details please review the Ubuntu Community Help on ChRoot

Use Group Policy Management  and set the following:

Computer Configuration > Policies > Administrative Templates > System > Verbose vs normal status messages > Enabled

• Visit http://get.adobe.com/flashplayer/otherversions/
• Select Linux (64bit or 32bit depending on what version of CentOS you installed)
• Select (.rpm)
• Click Download now

Once finished, select open with Package Installer, press OK, and input your root password when prompted.

Exit Firefox and reopen it and you’re done.

In an Administrator command prompt, run Setup.exe /b”C:\extracted”  (note there is intentionally not a colon after /b)

The GUI installer will decompress the .msi and 1033.mst files to the path specified, and present you with Next or Cancel. Choose Cancel and then Finish. (1033.MST is just an English language transform that is not really needed.)

You now have your files extracted from the Installshield exe so that you can use to deploy ShoreTel Communicator via a Group Policy Object. (GPO)

Unfortunately running Setup.exe /? will not help you. I found the /b in an Installshield manual. The files are also extracted to a GUID named folder in %temp% too, but this is a safer bet.

• Install Office 2010 to your liking on a PC
• Use Microsoft Update to install all the needed updates for that PC
• Use CollectUpdates.vbs to gather all installed Office updates and service packs (see TechNet)
• Copy the collected updates from %Temp%\Updates to the network installation point’s Updates folder

That’s it. Next time you install Office 2010 it will install all those updates during the initial installation. *This method has replaced slip streaming.

Trying to download the Address Book: Produces an Outlook client error 0×80200049 The operation failed.

You will notice that the OAB / GAL in cached mode is out of date, but the OAB / GAL in online mode is correct.

Note: This article assumes you have already created a Public folder database on Exchange 2010.

HOW TO FIX THIS

First check that your databases are pointing to the correct 2010 server for Default public folder database and Offline address book.

In EMC

Organization Configuration > Mailbox > Database Management tab > Properties on a DB > Client Settings tab

In Windows Explorer

Delete all files/directories INSIDE but not the directories themselves:

C:\Program Files\Microsoft\Exchange Server\V14\ExchangeOAB

C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\OAB

In EMC

Server Configuration > Client Access > select SERVER > In action pane: Reset Virtual Directory…

Browse… > select OAB (Default Web Site) and click OK.

Click Next, when prompted choose Yes to All and choose Finish when complete.

Wait 30 sec for AD to replicate the changes.

In a command prompt

iisreset (/noforce is optional, MS support never had me use it)

In Exchange Management Shell

Set-OABVirtualDirectory -Identity “OAB (Default Web Site)” -RequireSSL $true -ExternalURL “https://exchange.contoso.com/OAB”

Get-OABVirtualDirectory |fl

Verify your InternalURL (http) and ExternalURL (https) and RequireSSL True

In EMC

Organization Configuration > Mailbox > Offline Address Book tab > Properties on Default Offline Address Book > Distribution tab > Enable Web-based distribution > Add… > Choose your OAB on Exchange 2010 > Apply/OK

Right-click Default Offline Address Book > Update > Yes

In Services MMC

Restart the service: Microsoft Exchange File Distribution

(This will populate the OAB guid in C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\OAB)

In a command prompt

iisreset (/noforce is optional, again MS support never had me use it)

Here is this entire documentation in PDF format with screenshots to help.

• Install the WAIK for Windows 7
• Create C:\test\offline and C:\drivers directories
• Copy from Windows 7 DVD/ISO sources dir: the boot.wim and install.wim to C:\
• Copy/extract your mass storage drivers to C:\drivers (OCZ Revo 3 in this case)

Open the Deployment Tools Command Prompt as an Administrator, and run the following commands.

Install.wim portion:

1. Dism /Mount-Wim /WimFile:C:\install.wim /Index:1 /MountDir:C:\test\offline
2. Dism /Image:C:\test\offline /Add-Driver /Driver:C:\drivers\ocz10xx-1.2.0.10490\amd64 /Recurse /ForceUnsigned
3. Dism /Unmount-Wim /MountDir:C:\test\offline /Commit

Boot.wim portion (only needed for F6 type drivers used during initial setup):

1. Dism /Mount-Wim /WimFile:C:\boot.wim /Index:2 /MountDir:C:\test\offline     (note: This must be /Index:2 and is the part that replaces the old F6 method like in XP)
2. Dism /Image:C:\test\offline /Add-Driver /Driver:C:\drivers\ocz10xx-1.2.0.10490\amd64 /Recurse /ForceUnsigned
3. Dism /Unmount-Wim /MountDir:C:\test\offline /Commit

The steps above in each portion mount the image, add the driver, and then save/unmount the image.

Finally, use UltraISO (not free) and open the original ISO and drag and drop your new .wim files to the sources dir within UltraISO. When prompted, choose Yes to replace the files. After that you can burn the ISO. There is a command line utility called oscdimg that can be used to create ISO files for free, but that is beyond the scope of this article. Google is your friend in that case.

You can add other drivers but only the storage, OCZ in this example, really needs to be in the boot.wim file so you can install Windows to your SSD.

http://download.skype.com/SkypeSetupFull.exe

Note: Sometimes there is an auto update after installing the latest full version. This is normal behavior.

It would be nice if Skype made this easier to find on their site. This file comes in handy in case the normal Setup.exe fails to install.