Monday, 29 September 2014

Import the Power shell module for Configuration Manager 2012

PowerShell module for managing System Center Configuration Manager 2012 is not available by default in PowerShell Console... If you want to Import module for SCCM 2012, run the below command

001
Import-Module (Join-Path $(Split-Path $env:SMS_ADMIN_UI_PATHConfigurationManager.psd1)

If you are using SCCM console from different PCs, you have to copy the module file (ConfigurationManager.psd) from SCCM server or Go to File Menu of SCCM and Open PowerShell


Saturday, 20 September 2014

Virtual Machine Creation In Azure Using PowerShell


  • Azure Registration : As you know we have to register in azure to use all the stuff. Below is the azure sing up \ Sign In link. One month free trial available.
          Azure Sin Up \ Sign In
  • Azure PowerShell module Installation : You can download and Install Azure Powershell from the below URL. After the installation, you will be able to find a new console named Microsoft Azure Powershell on you start.

    Download Azure PowerShell module
  • Azure Publish settings file download and configure : We have to download our azure publish file from our azure subscription. Follow the below steps to do that..
PS C:\>Get-AzurePublishSettingsFile
PS C:\>

This command will take you to azure log in page as showing below. You will have to provide your azure credential which you have registered prior.
















Once you logged, you will be prompted to download azure public setting file.Save the publish settings file on your drive. Refer the below picture.
File name will be like (Free Trial-9-19-2014-credentials.publishsettings)



















Now we have to import the saved publish setting file using the below command. Command should point to 

the saved location. So please note the location of public setting file while downloading.



PS C:\> Import-AzurePublishSettingsFile 'C:\vivek\Free Trial-9-19-2014-credentials.publishsettings'

This command will install the certificate into your certificate store and will configure your subscription settings.
You can verify the configured subscription by typing the below command. It will display the Subscription ID 


PS C:\> Get-AzureSubscription

# Execution Result

SubscriptionId             : b96c19a1-83c0-4614-91bf-402074vf4ae7
SubscriptionName          : Free Trial
Environment                  : AzureCloud
SupportedModes            : AzureServiceManagement
DefaultAccount              : BD555B5D40D53783C2BC366E2CD49A49EA459906
Accounts                       : {BD555B5D40D53883C2BC366F2CD49A49EA459906}
IsDefault                        : True
IsCurrent                        : True

CurrentStorageAccountName : 

Now we have to select the subscription



PS C:\> Select-AzureSubscription -SubscriptionName "Free Trial"

# You can use (Get-AzureSubscription).SubscriptionName to get the subscription name.Make sure that you are typing the correct subscription name as displayed.. 

Verify the subscription using the below command

PS C:\> get-AzureSubscription -Default

PS C:\>

Affinity Group Creation And Set the Storage Account to be used by new affinity group 


Affinity Groups are a way you can group your cloud services by proximity to each other in the Azure data center in order to achieve optimal performance. When you create an affinity group, it lets Azure know to keep all of the services that belong to your affinity group as physically close to each other as possible. For example, if you want to keep the services running your data and your code together, you would specify the same affinity group for those cloud services. They would then run on hardware that is located close together in the data center. This can reduce latency and increase performance, while potentially lowering costs.


PS C:\> New-AzureAffinityGroup -Name "VivAffGrp" -Location "Southeast Asia" -Label "VIVEKRRLAB" -Description "My Affinity Group" -Verbose

#Execution Result

VERBOSE: 11:46:25 AM - Begin Operation: New-AzureAffinityGroup
VERBOSE: 11:46:28 AM - Completed Operation: New-AzureAffinityGroup

OperationDescription                             OperationId                                                          OperationStatus                                

--------------------                                         -----------                                                              ---------------                                
New-AzureAffinityGroup                           2c6aa8ee-c6eb-1dd6-b67a-213e1c6d0f0d             Succeeded
PS C:\>

Storage Account Creation : 

"To store files and data in the Blob, Table, Queue, and File services in Azure, you must create a Storage account in the geographic region where you want to store the data"


So we need to create a storage account to create VMs ( To save VHDs ) . Follow the below steps to do that. Sharing the present status of my storage account.


















Before creating storage account, we have to know which location has to be selected. So find out the list of location available in azure and select accordingly.


# Get the Location Name first
PS C:\> (Get-AzureLocation).Name
#Execution Result
South Central US
Central US
East US 2
East US
West US
North Europe
West Europe
East Asia
Southeast Asia
Japan West

We got some location list as shown above, and we are going to select "Southeast Asia" as our location.

After the creation of storage account, we have to disable Geo replication option (Optional) if you are using the LAB locally.

* Storage Account Name will accept only small letters and numbers. Do Not Give Capital Letter 



PS C:\>New-AzureStorageAccount -AffinityGroup "VivAffGrp" -StorageAccountName "vivekrrstorage" -Label "VIVEKRRLAB" -Description "My Storage Account" -Verbose

PS C:\> Set-AzureStorageAccount -StorageAccountName vivekrrstorage -GeoReplicationEnabled $false -Verbose


#Execution Result

VERBOSE: 10:45:59 AM - Begin Operation: Set-AzureStorageAccount
VERBOSE: 10:46:04 AM - Completed Operation: Set-AzureStorageAccount
OperationDescription                             OperationId                                      OperationStatus                                
--------------------                             -----------                                      ---------------                                
Set-AzureStorageAccount                          5239ec4f-18f3-1925-9f1d-5fa4a34561e9             Succeeded 



Storage Account is ready in Azure : Note the below storage account name
















Once we created the storage account, set it as like the current storage account to be used for your default subscription. Follow the below steps and confirm that the current storage account name (vivekrrstorage) is displayed in your subscription.


PS C:\> Set-AzureSubscription -SubscriptionName "Free Trial" -CurrentStorageAccountName "vivekrrstorage"

#Confirm that the subscription has been set or not


PS C:\> Get-AzureSubscription
#Execution Result
SubscriptionId                         : b96c19a1-83c0-4614-91bf-402074cf4ae7
SubscriptionName                   : Free Trial
Environment                            : AzureCloud
SupportedModes                    : AzureServiceManagement
DefaultAccount                       : BD555B5D40D53783C2BC366F2CD49A49EA459906
Accounts                                : {BD555B5D40D53783C2BC366F2CD49A49EA459906}
IsDefault                                 : True
IsCurrent                                : True
CurrentStorageAccountName : vivekrrstorage

Now you will be able to see the current storage account name has updated with its value (vivekrrstorage).


Cloud Service Creation:


Cloud Service: By creating a cloud service, you can deploy a multi-tier web application in Azure, defining multiple roles to distribute processing and allow flexible scaling of your application. A cloud service consists of one or more web roles and/or worker roles, each with its own application files and configuration. Azure Websites and Virtual Machines also enable web applications on Azure. The main advantage of cloud services is the ability to support more complex multi-tier architectures. For a detailed comparison,


Please note that there is no cloud service created yet..















PS C:\> New-AzureService -ServiceName "CloudServiceViv" -AffinityGroup "VivAffGrp" -Label "VIVEKRRLAB" -Description "My Cloud Service" -Verbose

#Execution Result

VERBOSE: 1:16:10 PM - Begin Operation: New-AzureService
VERBOSE: 1:16:14 PM - Completed Operation: New-AzureService
OperationDescription                                         OperationId                                                       OperationStatus                                            
--------------------                                                   -----------                                                              ---------------                                            
New-AzureService                                             edbcd0e0-867a-18e5-a215-2fd2a2937bb3                         Succeeded                                                  



Cloud Service is ready now ... You can type Get-AzureService to check the status..












                       

Get Ready To Create VMs  :)

The first step is to decide that, which Image (or OS) you are going to deploy in Azure. There are many Images available in azure gallery.So we need to find out the Image name to deploy it. If you want you can log in and check Image availability in Azure. Below is the VM gallery snap from Azure Portal


























Now we are going to fetch the same details through powershell


Get-AzureVMImage is the Cmdlet to retrieve all the available VMs Images from Azure Portal.. As per the above snap shot Windows Server 2012 R2 Datacenter is the Imagefamily Name of an Image. So first you go ahead and type Get-AzureVMImage and see how the out put is !!!


Image Family : Image Family is a Property field of Azure VM Image (Display Name)


PS C:\> Get-AzureVMImage
PS C:\>(Get-AzureVMImage).ImageFamily

#Execution Result

Visual Studio Professional 14 CTP 2 on Windows Server 2012 R2
RightScale Linux v13
RightScale Linux v13
RightScale Linux v14
JDK 6 on Windows Server 2012
JDK 6 on Windows Server 2012
JDK 7 on Windows Server 2012
JDK 7 on Windows Server 2012
JDK 8 on Windows Server 2012 R2
JDK 8 on Windows Server 2012 R2
JDK 8 on Windows Server 2012 R2
Oracle Database 11g R2 Enterprise Edition on Windows Server 2008 R2
Oracle Database 11g R2 Enterprise Edition on Windows Server 2008 R2
.....................................................................................................
more

#Total Images Available in Azure Portal


PS C:\>((Get-AzureVMImage).ImageFamily).count


#Execution Result

253


Have a check on any Images and see all the property. Below I am checking a Linux Image.The same way you can check a Windows Image by giving the Image Family Name.

First property is the Name of Image (Vhd)



PS C:\> Get-AzureVMImage | ? {$_.ImageFamily -eq "RightScale Linux v13"} | select -First 2
#Execution Result
ImageName                 : 0b11de9248dd4d87b18621318e037d37__RightImage-CentOS-6.2-x64-v5.8.8.1
OS                               : Linux
MediaLink                    : 
LogicalSizeInGB          : 10
AffinityGroup               : 
Category                     : Public
Location                      : East Asia;Southeast Asia;North Europe;West Europe;Japan West;Central US;East US;East US 2;West US
Label                          : RightImage CentOS 6.2 x64 v5.8.8.1
Description                 : CentOS 6.3 with RightLink 5.8.
Eula                            : http://support.rightscale.com/12-Guides/RightLink/RightLink_End_User_License_Agreeement
ImageFamily               : RightScale Linux v13
PublishedDate             : 8/28/2012 5:30:00 AM
IsPremium                   : False
IconUri                        : 
SmallIconUri               : 
PrivacyUri                   : http://www.rightscale.com/privacy_policy.php
RecommendedVMSize : 
PublisherName           : RightScale with Linux
OperationDescription : Get-AzureVMImage
OperationId                : 053fe9cd-7e9f-1a4c-a6d4-601184234ba6
OperationStatus         : Succeeded

Creation of Virtual Machine and Provisioning Configuration :


We are going to create a Windows Server VM. So first we need to find out the exact name of the VM using the below command. Refer the above Image Gallery Screen Shot.



PS C:\> $SelectedVM = Get-AzureVMImage | ? {$_.ImageFamily -eq "Windows Server 2012 R2 Datacenter"} | select -last 1

Here I am selecting the last Image of "Windows Server 2012 R2 Datacenter". There are different images available in azure portal for the same OS. Most probably last Image will be the latest image released from Microsoft. You can check the published date as well to confirm the latest Image.

  • Creating Virtual Machine Configuration:

$Image = $SelectedVM.Imagename



PS C:\>$Configuration = New-AzureVMConfig -Name "VIVServer01" -InstanceSize "small" -ImageName $Image


















  • Adding Provisioning Configuration :

$UserName = "vivadmin"
$Password = "Image@123"

PS C:\>Add-AzureProvisioningConfig -Windows -AdminUsername $Username -Password $Password -VM $Configuration

Now the configuration field also filled















  • Networking Part
Right Now I am not creating Virtual Network through Powershell as there is no cmdlet to do that. So I have already created a VNet in my azure platform. Only we need to add those details to our VM Configuration.
Below is my VNet Configuration In Azure Portal.


















Adding IP Address and Sub-net Name to VM Configuration : 

$IpAddress = "10.0.0.5"

PS C:\>Set-AzureStaticVNetIP -IPAddress $IpAddress -VM $Configuration
PS C:\>Set-AzureSubnet -SubnetNames DC001 -VM $Configuration
#Just Verify the Configuration

PS C:\>$Configuration.ConfigurationSets

















The Final Steps : VM Creation : 

PS C:\>New-AzureVM -ServiceName "CloudServiceViv" -VMs $Configuration -VNetName "MyNET" -Verbose












Now our New VM ( VIVServer01 ) Is ready on Azure  !!!














Now you can start using the new VM by connecting from Azure portal or through Powershell (PS Session). 

I am just ceating a VM in azure portal... Please Visit below URL (DexterPosh) to know more about Powershell + Azure Deploy





Friday, 19 September 2014

How to Make a Bootable USB Using PowerShell !!!

Try to use powershell for all the command line operation instead of cmd. Be familiar in PS

  • Open PowerShell as administrator
  • Type Get-disk  To get the details of connected disk
  • Find out your Pen drive form the list


  • Mount-Diskimage -Imagepath <Imagepath> : To mount the ISO Image
  • Double click on Image if you are using Win-8  to mount the ISO








  • Clear-disk -number 1 -removedata
  • Be careful while selecting disk number
  • This cmdlet will clear the disk and remove all the data











  • Now we have to create New partition.
  • New-partition -Disknumber 1 -usemaximumsize -Isactive:$true
  • Make sure that Drive letter is assigned properly and then format the disk
  • Format-volume -Filesystem NTFS -Driveletter H











  • And below is the final step to make the drive bootable
  • Bootsect.exe /NT60 H:
  • This command will update the boot code on the partition

  • Pen Drive is now bootable
  • Open the ISO Image and copy all the files in to pen drive
  • Make changes in BIOS to boot from Pen Drive


Tuesday, 9 September 2014

Help Vs Get-Help In PowerShell

At the first look there is no difference between help and get-help. But they are entirely different command.. I am giving some examples to understand about help and get-help

001
002
003
004
005
006
007
008
009
Get-Command *help*

CommandType     Name                            ModuleName
-----------     ----                            ----------
Function        help                                      
Cmdlet          Get-Help                        Microsoft.PowerShell.Core
Cmdlet          Save-Help                       Microsoft.PowerShell.Core
Cmdlet          Update-Help                     Microsoft.PowerShell.Core
Application     help.exe

From the above example, you will be able to understand the Command types of help and get-help
Help is a function and Get-help is a Cmdlet... And there is no Alias for get-help. Man is the alias for help. Please go through the below examples..

001
002
003
004
005
006
007
008
009
010
011
012
013
014
015
Get-Alias -Definition Help

CommandType     Name                                               ModuleName
-----------     ----                                               ----------
Alias           man -> help                                                  

Get-Alias -Definition Get-Help

Get-Alias : This command cannot find a matching alias because an alias with the definition 'Get-Help' does not exist.
At line:1 char:1
+ Get-Alias -Definition Get-Help
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Get-Help:String[Get-Alias], ItemNotFoundException
    + FullyQualifiedErrorId : ItemNotFoundException,Microsoft.PowerShell.Commands.GetAliasCommand

Type Get-Content function:\help If you want to see the content inside the function.