Archive for category Uncategorized

Dell vWorkspace 8.5 review


Marius Sandbu - IT blog

A cool year so far to be working in IT! alot of new tech been released and I have a lot of catching up to do. One of this is vWorkspace 8.5 which was released a couple of weeks ago.

For those that aren’t aware of what it is, can read some of my previous posts regarding vWorkspace or see a bit from this Dell FAQ: http://en.community.dell.com/techcenter/virtualization/vworkspace/b/vworkspace-blog/archive/2014/12/09/latest-release-of-vworkspace-8-5-faq-39-s

http://msandbu.wordpress.com/2014/04/20/introduction-to-dell-vworkspace/

Now vWorkspace has been an underdog to the other competition like Vmware View and Citrix XenDesktop, but with this release they have removed some of the gap that the competition might have.

So what’s included and what’s new in this release?

* Foglight for virtualization
Foglight is a monitoring tool which allows us to monitor our entire virtual infrastructure even if it us running on Vmware or Hyper-V

Permalink til innebygd bilde it also has a good integration directly to vWorkspace which allows us to drill…

View original post 478 more words

Advertisements

Leave a comment

Dell vWorkspace EOP–Configuration


vWorkspace administrators must read .

Marius Sandbu - IT blog

For those who do not know what vWorkspace is, take a look at my previous blogpost regarding vWorkspace –> http://msandbu.wordpress.com/2014/04/20/introduction-to-dell-vworkspace/

EOP (Enhanced Optimized Protocol) is an enhancement to the RDP protocol which Dell (or Quest) have developed which is a part of vWorkspace. Now Microsoft has made alot of improvements to the RDP procotol in 2012 and 2012 R2, but it is nowhere near Citrix in how it performs over WAN and the ability to deliver high-graphic content. EOP contains mulitple enhancements to the procotol to even the difference, like:

EOP Xtream. Accelerates RDP and EOP traffic on wide area networks (WANs). This provides for an improved user experience by providing faster RDP screen responses and improved performance of all EOP features.

EOP Print. A single-driver printing solution that satisfies both client-side and network printing needs in a vWorkspace environment.

EOP Audio. Enables support for applications that require the…

View original post 398 more words

Leave a comment

Introduction to Dell vWorkspace


Marius Sandbu - IT blog

Lately there has been alot of fuzz regarding Vmware and their release with Horizon 6 suite with terminal server based solution, and if we rewind one month back in time we also have the latest XenDesktop release from Citrix which contains Hybrid cloud provisioning features.

Now both Citrix and VMware are both good options and of course Microsoft themselves are becoming more focused regarding delivering apps and desktops to users, with the latest release and with of course remote clients for Apple and Android.

There is also other products within this segment, one of them which I find interesting in particular is Dell vWorkspace.

vWorkspace is part of the formerly known Quest Software portfolio which is now part of Dell. vWorkspace has much of the same features such as any other VDI/RDSH product but it has some interesting features as well, such as

* Support for Linux VMs
* EOP…

View original post 786 more words

Leave a comment

View Mailboxes in Exchange Server 2007 who Exceed Quota Limit


Mailbox quotas help control the size of mailboxes, For example, would you like to know which mailboxes have reached their prohibit send receive quota, Or view the mailbox size and quota status of a specific mailbox?

You can do all that with the Get-Mailbox and Get-MailboxStatistics Exchange PowerShell cmdlets.
Get-Mailbox -ResultSize Unlimited | Get-MailboxStatistics | where {$_.StorageLimitStatus -notlike "BelowLimit*"} | select DisplayName,LegacyDN,DatabaseName,StorageLimitStatus|Export-Csv c:\ExceedQuota.csv

The above script will loop through each Mailboxes and will get each Mailbox Statistics where their StorageLimitStatus not BelowLimit.

The Get-MailboxStatistics has a property where you can fetch each a property with Where statement and braces bracket {} to get the StorageLimitStatus Property.

The result of the above script is the below table;

DisplayName LegacyDN DatabaseName StorageLimitStatus
Full Display Name /O=Organization/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=Alias Students-DB10 ProhibitSend

Manual work has to be done to remove the LegacyDN and keep only the Alias CTRL+H find what and Replace All is a good to delete the entire LegacyDN name and keep only the Alias.

You can use another script to move the mailbox from one Database which has got a quota limited quota to a higher Database which has higher quota.

In order to move the Mailbox to higher quota Database, you need to know the Database Storage Limit Size. You can achieve this by running the Get-MailboxDatabase cmdlet in Exchange PowerShell and pipe it with the property of ProhibitSendReceiveQuota
 Get-MailboxDatabase | select Name, StorageGroup, ProhibitSendReceiveQuta | Export-CSV C:\DBQuota.csv

Name StorageGroup ProhibitSendReceiveQuota
Staff-DB1-H MAILSERVER\Staff-SG 2355MB
Staff-DB2-N MAILSERVER\Staff-SG 1111520KB
Staff-DB3-L MAILSERVER\Staff-SG 515520KB
Students-DB1 MAILSERVER\Students-SG 1000MB
Students-DB2 MAILSERVER\Students-SG 100MB
Students-DB3 MAILSERVER\Students-SG 200MB
Students-DB4 MAILSERVER\Students-SG 311999KB
Students-DB5 MAILSERVER\Students-SG 1300000KB
Students-DB6 MAILSERVER\Students-SG2 400MB
Students-DB7 MAILSERVER\Students-SG2 522000KB
Students-DB8 MAILSERVER\Students-SG2 800MB
Students-DB9 MAILSERVER\Students-SG2 919200KB
Students-DB10 MAILSERVER\Students-SG2 1024160KB
Staff-DB4-O MAILSERVER\Staff-SG 5000MB
Students-DB11 MAILSERVER\Students-SG3 200MB
Students-DB12 MAILSERVER\Students-SG3 200MB
Students-DB13 MAILSERVER\Students-SG3 200MB
Students-DB14 MAILSERVER\Students-SG3 200MB

Now it’s time to move the Mailboxes from their current Database where has got limited quota to the higher Databases which has higher quota.

In order to move the require users from one Database to another, you need to put their Alias/EmailID into a text file to be called by another script and start moving the mailbox to the target Database.

You can filter the first CSV export by Database Column to get all the users in the limited quota database, copy only the  Alias/EmailID to a text file and use the below script to move them to the target Database;


#############################
# Move-Multiple-Mailbox.ps1 #
# Created By Assaf Miron #
# Date : 06/11/07 #
#############################

Param(
[String]$TargetDB,
[String]$FileToOpen,
[Boolean]$ValidateOnly=$False
)

function IsHelpRequest
{
param($argument)
return ($argument -eq "-?" -or $argument -eq "-help");
}

# Function that displays the help related to this script following
# the same format provided by get-help or -?
Function Usage
{
@"

NAME:
`tMove-Multiple-Mailbox.ps1 [-FileToOpen][-TargetDB]

SYNOPSIS:
`tMoves a list of mailboxes listed in an Excel File to
`ta specific Database.

SYNTAX:
`tMove-Multiple-Mailbox.ps1
`t`t[ -FileToOpen ]
`t`t[ -TargetDB ]
`t`t[ -ValidateOnly [True/False] ]

PARAMETERS:
`t-FileToOpen (required)
`t`tAn Text File wich Contains Principle Names of Users to Move
`t-TagretDB (required)
`t`tTarget Databse Name
`t-ValidateOnly (optional)
`t`tDoesn't move the mailboxes but checks if they can move to the target DB

`t-------------------------- EXAMPLE 1 --------------------------

C:\PS> .\Move-Multiple-Mailbox.ps1 -FileToOpen "C:\UsersToMove.txt" -TargetDB "Students-DB6"

`t-------------------------- EXAMPLE 2 --------------------------

C:\PS> .\Move-Multiple-Mailbox.ps1 -FileToOpen "C:\UsersToMove.txt" -TargetDB "Students-DB6" -ValidateOnly $true

REMARKS:
`tThe Move Mailbox accours with the Max threads Parameter
`tit will not move mailboxes that have errors
`tor mailboxes that need to preserve thier size.

"@
}

####################################################################################################
# Script starts here
####################################################################################################

# Check for Usage Statement Request
$args | foreach { if (IsHelpRequest $_) { Usage; exit; } }

$arrMailboxes = @()

# Validate the parameters
If ($TargetDB -eq "") { Usage; exit; }
Else {
If ($FileToOpen -eq "") { Usage; exit; }
Else {
write-host $FileToOpen

$arrMailboxes = Get-Content $FileToOpen

Write-Host "About to move"$arrMailboxes.Count"Mailboxes to"$TargetDB
$Ans = Read-Host "is This information Correct ? `n[Yes,No]`nDefault(Yes)"
If ($Ans.Contains("n")) { exit; }
If ($ValidateOnly -eq $True)
{
$arrMailboxes | Move-Mailbox -TargetDatabase $TargetDB -MaxThreads 16 -ValidateOnly
}
Else
{
$arrMailboxes | Move-Mailbox -TargetDatabase $TargetDB -MaxThreads 16
}
}
}

, , , , , , , ,

Leave a comment

Get-ADUser – PowerShell & Active Directory


Well, Get-ADUser is a useful PowerShell command to get everything you required from single object in Active Directory. For instance, I have around 2500 objects in Active Directory and these objects are populated with an Employee ID in the Description Filed.

I have a requirement where I want to fetch the Name, Email ID and the Description ‘Employee ID’

Get-ADUser has several approaches to fetch this requirement, but  in here I will talk about the main thing which got my requirement fulfilled.

Get-Content C:\EmployeeID.txt | ForEach-Object { Get-ADUser -Filter {Description -eq $_} -Properties EmailAddress, Description | Select-Object Name, EmailAddress, Description } | Export-Csv C:\ID.csv -NoTypeInformation

All done, this will give a result of a CSV File with Name, Email Address and Description.

Thanks,

2 Comments

(DUP!) Duplicate Ping when you ping VMKernel PortGroup within ESX Host


Hello,

Have you ever encountered a duplicated ping when you try to ping the iSCSI PortGroups or pinging the ESX Host Itself from vCenter?

In my case I have this issue when I try to ping from ESXi5.0 host to an iSCSI Target.

SAN Storage Configuration:

IBM DS3512 with two Controllers, each with 4 iSCSI Ports.

CTRL-1:
Port-3: 10.10.30.1
Port-4: 10.10.40.1
Port-5: 10.10.50.1
Port-6: 10.10.60.1

CTRL-2:
Port-3: 10.10.30.2
Port-4: 10.10.40.2
Port-5: 10.10.50.2
Port-6: 10.10.60.2

When I try to ping each of the iSCSI Ports IP Address, I got

64 bytes from xxx.xxx.xxx.xxx: icmp_seq=4 ttl=128 time=0.xxx ms (DUP!)

ESX iSCSI Configuration:

vSwitch with 4 VMKernels PortGroup for iSCSI.

iSCSI-30 10.10.30.x

iSCSI-40 10.10.40.x

iSCSI-50 10.10.50.x

iSCSI-60 10.10.60.x

By default, vSwitch will take Route Based on the Originating port ID.

I resolved this issue by:

Changing from Route based on the Originating Port ID to Route based on IP Hash. And I set each VMKernel Port active on one nic only instead of two “Default”

VMNIC3 active for iSCSI-30 and iSCSI-40 because this NIC connected to Switch-1 as well as both iSCSI Ports.

VMNIC9 active for iSCSI-50 and iSCSI-60 because this NIC connected to Switch-2 as well as both iSCSI Ports.

(DUP!) has disappeared after doing this :)

, , , , ,

Leave a comment

(DUP!) Duplicate Ping when you ping VMKernel PortGroup within ESX Host


Hello,

Have you ever encountered a duplicated ping when you try to ping the iSCSI PortGroups or pinging the ESX Host Itself from vCenter?

In my case I have this issue when I try to ping from ESXi5.0 host to an iSCSI Target.

SAN Storage Configuration:

IBM DS3512 with two Controllers, each with 4 iSCSI Ports.

CTRL-1:
Port-3: 10.10.30.1
Port-4: 10.10.40.1
Port-5: 10.10.50.1
Port-6: 10.10.60.1

CTRL-2:
Port-3: 10.10.30.2
Port-4: 10.10.40.2
Port-5: 10.10.50.2
Port-6: 10.10.60.2

When I try to ping each of the iSCSI Ports IP Address, I got

64 bytes from xxx.xxx.xxx.xxx: icmp_seq=4 ttl=128 time=0.xxx ms (DUP!)

ESX iSCSI Configuration:

vSwitch with 4 VMKernels PortGroup for iSCSI.

iSCSI-30 10.10.30.x

iSCSI-40 10.10.40.x

iSCSI-50 10.10.50.x

iSCSI-60 10.10.60.x

By default, vSwitch will take Route Based on the Originating port ID.

I resolved this issue by:

Changing from Route based on the Originating Port ID to Route based on IP Hash. And I set each VMKernel Port active on one nic only instead of two “Default”

VMNIC3 active for iSCSI-30 and iSCSI-40 because this NIC connected to Switch-1 as well as both iSCSI Ports.

VMNIC9 active for iSCSI-50 and iSCSI-60 because this NIC connected to Switch-2 as well as both iSCSI Ports.

(DUP!) has disappeared after doing this :)

, , , , ,

Leave a comment