Saturday, May 19, 2012

Procedure to make a bootable VMware ESXi 5 USB stick

Here is a simple procedure to make a bootable VMware ESXi 5 USB stick in Windows and perform a scripted unattended VMware ESXi 5 installation. Here are the 5 steps:

Step 1

Be sure removing all partitions and format a FAT32 partition on the USB stick by using the following command:
Open the command prompt and enter the following commands:
diskpart (make sure you run diskpart as administrator) 
list disk (list the disk in your system including the USB) 
select disk USB number 
clean 
create partition primary 
active 
format fs=fat32 quick
assign
exit

Step 2


Download Unetbootin here

Step 3


Start the UNetbootin tool
  1. Select Diskimage
  2. Browse to your downloaded vSphere 5 iso
  3. Select the USB drive
  4. Select the Fat32 partition driveletter
  5. Click OK














In less than a minute you will have a bootable usb media with the vSphere 5 installation files on it!


Saturday, May 12, 2012

Enable password protection on mobile devices with Exchange




The following Exchange policies are supported

  • Enforce password on device
  • Minimum password length
  • Maximum failed password attempts
  • Require both numbers and letters
  • Inactivity time in minutes

The following Exchange 2007 policies are also supported

  • Allow or prohibit simple password
  • Password expiration
  • Password history
  • Policy refresh interval
  • Minimum number of complex characters in password
  • Require manual syncing while roaming
  • Allow camera
  • Require device encryption
Enable password on mobile devices with an Exchange policy
  1. Open the Exchange Management Console
  2. Expand the Organization Configuration
  3. Click on Client Access













In the
Action menu click New Exchange ActiveSync policy.



















Type
Remote Device Policy as new policy name.
  • Select Require password
  • Allow simple password
  • Minimum password length (4)
  • Password expiration days (90)
  • Enforce password history (3)













The new policy is created now.

Apply the new ActiveSync policy to an tablet or smartphone user

Select an mobile device user.





















Select the
Mailbox Features tab.
Double click on Exchange ActiveSync.





















Click on the
Browse button.
Select the new created policy (Remote Device Policy).

The new policy will be applied to the mobile device when an Exchange ActiveSync connection is made.

Remote data wipe

When an mobile device is stole you can wipe the data remote.
You can do this as an administrator at the following way.
  1. In the Exchange Management Console select the stolen device user
  2. From the Action menu click on Manage mobile device
  3. Click on the Wipe data button to wipe all the data from the mobile device.
As end user you are able to wipe all the data from your stolen device from Outlook Web Access.



Friday, May 11, 2012

Which Version of Exchange Am I Running?

[PS] C:\>Get-ExchangeServer | fl name, *version*

Name                : EX2007
AdminDisplayVersion : Version 8.2 (Build 176.2)
ExchangeVersion     : 0.1 (8.0.535.0)
Build numbers and release dates for Exchange Server
Exchange Server  4.0                                4.0.837                  
    April 1996 
Microsoft Exchange Server  4.0 (a)                  4.0.993                  
    August 1996 
Microsoft Exchange Server  4.0 SP1                  4.0.838                  
    May 1996 
Microsoft Exchange Server  4.0 SP2                  4.0.993                  
    August 1996 
Microsoft Exchange Server  4.0 SP3                  4.0.994                  
    November 1996 
Microsoft Exchange Server  4.0 SP4                  4.0.995                  
    April 1997 
Microsoft Exchange Server  4.0 SP5                  4.0.996                  
    May 1998 
Microsoft Exchange Server  5.0                      5.0.1457                 
    March 1997 
Microsoft Exchange Server  5.0 SP1                  5.0.1458                 
    June 1997 
Microsoft Exchange Server  5.0 SP2                  5.0.1460                 
    February 1998 
Microsoft Exchange Server  5.5                      5.5.1960                 
    November 1997 
Microsoft Exchange Server  5.5 SP1                  5.5.2232                 
    July 1998 
Microsoft Exchange Server  5.5 SP2                  5.5.2448                 
    December 1998 
Microsoft Exchange Server  5.5 SP3                  5.5.2650                 
    September 1999 
Microsoft Exchange Server  5.5 SP4                  5.5.2653                 
    November 2000 
Microsoft Exchange 2000 Server                      6.0.4417                 
    October 2000 
Microsoft Exchange 2000 Server (a)                  6.0.4417                 
    January 2001 
Microsoft Exchange 2000 Server SP1                  6.0.4712                 
    July 2001 
Microsoft Exchange 2000 Server SP2                  6.0.5762                 
    December 2001 
Microsoft Exchange 2000 Server SP3                  6.0.6249                 
    August 2002 
Microsoft Exchange 2000 Server post-SP3             6.0.6487                 
    September 2003 
Microsoft Exchange 2000 Server post-SP3             6.0.6556                 
    April 2004 
Microsoft Exchange 2000 Server post-SP3             6.0.6603                 
    August 2004
Microsoft Exchange 2000 Server post-SP3             6.0.6620.5               
    March 2008    
Microsoft Exchange 2000 Server post-SP3             6.0.6620.7               
    August 2008
Microsoft Exchange Server  2003                     6.5.6944                 
    October 2003 
Microsoft Exchange Server  2003 SP1                 6.5.7226                 
    May 2004 
Microsoft Exchange Server  2003 SP2                 6.5.7638                 
    October 2005
Microsoft Exchange Server  2003 post-SP2            6.5.7653.33              
    March 2008
Microsoft Exchange Server  2003 post-SP2            6.5.7654.4               
    August 2008   
Microsoft Exchange Server  2007                     8.0.685.24 or 8.0.685.25 
    December 2006 
Microsoft Exchange Server  2007 SP1                 8.1.0240.006             
    November 2007
Microsoft Exchange Server  2007 SP2                 8.2.0176.002             
    August 2009
Microsoft Exchange Server  2007 SP3                 8.3.0083.006
                  June  2010
Microsoft Exchange Server  2010                     14.00.0639.021
                  October 2009
Microsoft Exchange Server  2010 SP1                 14.01.0218.015
                  August 2010

Friday, April 20, 2012

Enable Federation with Lync Online and Lync On-Premise

On-premise domain has to enable Federation with Lync Online to get this working.

Option#1 :  Add the HostingProvider service entry: 
From your Lync Front End server, launch the Lync Management Shell. Create a new Hosting Provider entry for Lync Online using the following command:
New-CSHostingProvider –identity LyncOnline –ProxyFqdn sipfed.online.lync.com –Enabled $True
Identity                                                  : LyncOnline
Name                                                   : LyncOnline
ProxyFqdn                                           : sipfed.online.lync.com
VerificationLevel                                 : AlwaysVerifiable
Enabled                                               : True
EnabledSharedAddressSpace         : False
HostsOCSUsers                                  : False
IsLocal                                                   : False

Option#2 : Use Direct Federation : Add the Lync Online Allow domain entry with ProxyFqdn. ( Run the following two commands )
New-CSAllowedDomain –identity onlinedomain.com
Identity                                                   : onlinedomain.com
Domain                                                  : onlinedomain.com
ProxyFqdn                                             :
Set-csAllowedDomain onlinedomain.com –ProxyFqdn sipfed.online.lync.com

Open Federation settings will not work with Lync Online domain. If the on-premise Lync Domain tries Open federation with a Lync Online domain: The Edge server rejects the communication as the host providing the service mismatch.