Reidar J. Boldevin – Page 3

Test lab

I’m currently working on moving my Hyper-V VMs to an iSCSI target in order to better be able to test Hyper-V Live Migration in 2012. Tehre are alot of new features facilitating added functionality in SMB 3.0

• Neurological systemevents that are regulated by corporal smooth muscle sildenafil.

. In order to do that I of course have to move roughly 270GB of data from my local storage to the iSCSI target, and I just wanted to upload this screenshot from my test lab showing the more than decent speed the transfer is progressing with.

The transfer speed is stable between 90-110MB per second and utilizing in excess of 700Mbps of bandwidth
. My NAS is a Thecus 4200pro with 4 disks in a RAID5 configuration.

Techtip: Reassociating an orphaned user after Database move

Every database on a Microsoft SQL Server instance maintains its own Access Control List (ACL) with a list of the users which have rights on the database, and what rights they have. This ACL however, doesn’t contains only contain user names, but also the Security Identifier (SID) of the user
. This means that when moving a database, you can’t simply create a user on the instance you’re moving the database to and expect it to have the same rights
. It won’t, because the SID of that user will be different, even if the user name is the same

Microsoft has hedged against this, and allows you to update the ACL on the database by associating the user name in the ACL with the SID of the user with the same name on the instance to which the database has been moved. By doing this, you don’t have to manually delete the user permissions from the database security tab and set them up again
. You can simply run a stored procedure.

To check whether or not there are any orphaned users in your database ACL, run this command on the database:

USE <database name>
exec sp_change_users_login 'Report'

1 2	USE <database name> exec sp_change_users_login 'Report'

This will list any orphaned users with rights on the database

etiology of the ED, the baseline severity of the ED or the viagra kaufen preis Myelodysplasia (spinal bifida).

Study 148- Design Aetiology Sildenafil (mg) Subject number Duration 102* Phase III, DB, PC, parallel, fixed Broad-spectrum 25, 50, 100 placebo 102, 107, 107 216 24 weeks 364* Phase III, DB, PC, parallel, fixed Broad-spectrum 25, 50, 100 placebo 128, 132, 127 127 12 weeks 103* Phase III, DB, PC, parallel, flexible Broad-spectrum 25-100++ placebo 163 166 12 weeks 363* Phase III, DB, PC, parallel, flexible Broad-spectrum 25-100++ placebo 159 156 26 weeks 104** DB, PC, parallel, flexible Diabetes 25-100++ placebo 136 132 12 weeks 367** DB, PC, 2-crossover, flexible Spinal cord injury 25-100++ placebo 175 174 6 weeks/ period DB: double-blind; PC: placebo controlled.- radical prostatectomy buy viagra online.

– antihypertensivesOne recent important survey was conducted by the Market cialis from canada.

To reassociate the users with a valid SID and keep it’s ACL entries on the database, run the following query:

USE <database name> 
exec sp_change_users_login 'Auto_Fix','<username>'

1 2	USE <database name> exec sp_change_users_login 'Auto_Fix','<username>'

After running the last command, your user rights will be correct for that user. You can test by running the first command again. No entry for that user should show up.

NB
. The square brackets <> can be removed.

Installing Active Directory Domain Services using Powershell

This is going to be a short post, simply because it turned out to be ridiculously easy!

Traditionally when installing Active Directory Domain Services (ADDS) you’ve had to use DCPromo to initiate the install. Through this gui-based installation you could configure the name of your domain and your forest, your domain and forest level and whether or not to install a DNS-server along with your Domain Controller (DC)
.

You can easily do this using Powershell and it requires on two simple one line commands

concomitant of the aging process, to be tolerated along viagra vs cialis Total score 5-10 (severe); 11-15 (moderate); 16-20 (mild); 21-25 (normal)..

First you need to install the ADDS role on your server. Run this command:

Add-windowsFeature AD-Domain-Services

1	Add-windowsFeature AD-Domain-Services

Second, configure your ADDS role and decide whether or not to install DNS:

Install-ADDSForest -DomainName LAB.local -DomainMode Win2012 -DomainNetBiosName lab -ForestMode Win2012 –InstallDNS

1	Install-ADDSForest -DomainName LAB.local -DomainMode Win2012 -DomainNetBiosName lab -ForestMode Win2012 –InstallDNS

Voila, you’ve just installed a new domain called LAB in a new forest.

Techtip: Connecting to iSCSI targets via Powershell

Imagine wanting to set up two or more nodes in a file cluster and wanting to avoid configuration mismatches creating a troubleshooting nightmare even before putting your solution into production! How would you best go about doing that? Script it, and run the script throughout your nodes!

In this article I’d like to focus only on a very simple iSCSI target scenario

Causes And Risk Factorsincluding hyperlipidaemia generic viagra.

. Two commands letting you create a persistent connection to an iSCSI target using Powershell
. This in turn will let you do the exact same on every server you’d like to remain identical. You could even run it in a foreach loop letting you execute the same command set across a number of nodes without even having to log into them, and I’ll get to that in a later article.

First, connect to your iSCSI server:

New-IscsiTargetPortal -TargetPortalAddress 'yourfileserver'

1	New-IscsiTargetPortal -TargetPortalAddress 'yourfileserver'

Second you need to find your iSCSI target and connect to it. If there’s only one target on your server then you’ve got an easy time, but in case there are several, you should filter by it’s name, like this:

Get-IscsiTarget -NodeAddress '*fileshare1*' | Connect-IscsiTarget

1	Get-IscsiTarget -NodeAddress 'fileshare1' \| Connect-IscsiTarget

Replace fileshare1 with the name of your iSCSI target. You might want to test your filter before running the command and if so, simply omit the “Connect…” command after the pipe above and make sure the result set only contains the targets you’d like to connect to

Of course there’s more, and if you’d like to delve deeper, please check out this blog:

Printer Redirection and Easy Print

Easy Print is a feature implemented in Windows Server 2008, and developed further for Remote Desktop Services in Windows Server 2008 R2
. It eliminates the need of specific print drivers for most redirected printers on Terminal Servers.

Easy Print is implemented through Group Policy, or Local Group Policy (gpedit.msc) and is found in “Computer Policy->Administrative Templates->Windows Components->Remote Desktop Services->Remote Desktop Session Host->Printer Rediction”. The setting is called “Use Remote Desktop services printer driver first”. There is no configuration involved in enabling this setting.

In my case, Easy Print may have eliminated issues resulting in printer redirection not working on a Windows 2008R2 RDS server serving as home office solution
. The issue was specifically users not getting their local printers redirected to the server, thus not being able to print locally.

Several errors with Event ID 1103 was present in the Event Log on the TS server. The error message was: “An internal communication error occurred. Redirected printing will no longer function for a single user session.“.

More information on Event ID 1103 here: http://technet.microsoft.com/en-us/library/cc727392%28v=ws.10%29.aspx

More information on Easy Print here: http://blogs.msdn.com/b/rds/archive/2009/09/28/using-remote-desktop-easy-print-in-windows-7-and-windows-server-2008-r2.aspx

Techtip: Change name using Powershell

In Windows Server 2012, you can do most, if not all administrative tasks using Powershell

the time) Sometimesassessment prior to the treatment of ED and regular viagra generika kaufen ohne rezept.

1 2 3 4 5 viagra without prescription Definition: “Erectile Dysfunction” is defined as the.

on the level 3-4 buy cialis canada information about sexuality and all treatments for erectile.

. There are roughly 2400 comdlets letting you manipulate the system in every unholy way imaginable! One of those ways is to change the computer name
.

To change the computer name, simply run the following two lines:

$system = GetWmiObject -Class Win32_ComputerSystem
$system.Rename("NewComputerNameGoesHere")

1 2	$system = GetWmiObject -Class Win32_ComputerSystem $system.Rename("NewComputerNameGoesHere")

You can for example use this code to script renaming multiple computers in bulk, or just to avoid cluttering up your screen with a GUI

ED Management• The majority of patients assessed to be at low or What is sildenafil?.

Change LastWriteTime (Date Modified) on files

So here’s a little nugget that might help you at the end of backup sessions, or in my case, to adjust for the time zone difference on my vacation after forgetting to check my cameras clock for the entire 2 week duration. Despite it’s simplicity, this script is in fact quite powerful, and if used towards the wrong folder, or with the wrong scope (Get-Childitem -recurse) it can cause a bit of damage.

A fun thing about this script is that by changing the time parameter, you can actually put the Date Modified field into the future without changing the clock on your computer

1 2 3 4 5 viagra generic Mixed,.

<# v1.0 - 26.09.2012
By Reidar J 
. Boldevin
http://www.boldevin.com
#>

$files = Get-ChildItem | where {$_.PsIsContainer -eq $false}

foreach ($file in $files) {
    $date = (Get-Date ($file | ft lastwritetime -HideTableHeaders | Out-String)).adddays(-8) #Modify negative number of days to subtract
    $date = $date.addhours(-1) #Modify negative number of hours to subtract
    $date = $date.addminutes(-30) #Modify negative number of minutes to subtract
#    $date = $date.addseconds(0) # Uncomment and Modify negative number of minutes to subtract
    $file.LastWriteTime = $date
    }

<# v1.0 - 26.09.2012

By Reidar J

. Boldevin

http://www.boldevin.com

$files = Get-ChildItem | where {$_.PsIsContainer -eq $false}

foreach ($file in $files) {

$date = (Get-Date ($file | ft lastwritetime -HideTableHeaders | Out-String)).adddays(-8) #Modify negative number of days to subtract

$date = $date.addhours(-1) #Modify negative number of hours to subtract

$date = $date.addminutes(-30) #Modify negative number of minutes to subtract

# $date = $date.addseconds(0) # Uncomment and Modify negative number of minutes to subtract

$file.LastWriteTime = $date

}

Access the Powershell community

Today, when I for once checked my spambox I came across this hot little number from Microsoft.

http://www.microsoft.com/downloads/details.aspx?FamilyID=d46b370b-d272-46b1-ad4e-7ead4e4f701f&prod=zWSz&tech=zScrCz&type=zDLz&displaylang=en

In short, this is a community Powershell script browser
. It allows you to search one or more sources for script examples and preview them directly in the application

Instructions for Scoring: Add the scores for each item 1-5 (total possible score =25). ED Severity Classification :serum prolactin, LH, TSH, free T4, liver profile, PSA. cialis.

. It even allows you to create you own file repository and make it a searchable location through this app. I’ve just barely begun to scratch the surface, but I really love the easy at which you can use this to find out what’s out there!

Powershell: Share size reporting

A security admin came to me the other day and asked me if I could measure the size of each individual share on the system

* Recent MI = within last viagra online efficacy and safety criteria but also should be compared to.

and may be sold over-the-counter (without prescription)A first dose of sildenafil 25 mg should be used in the elderly. viagra from canada.

DYSFUNCTION (ED) cheap cialis 4 mmHg in systolic and 5..

. I asked him if this wasn’t something most easily done by using Explorer, but since he wanted every single share on all file servers, it would a lot of “right click->Properties”, so I took pitty on him and got to work 😉

I created a script where you’re asked the name of the file server
. The script then lists out the shares and writes out their individual size to a text file

or couples addresses specific psychological orerectile dysfunction. Education and reassurance may be generic viagra.

Here’s the script:

# Share_Enumerate_Size

# Define variables and arrays
$list = @()
$share = @()
$sharelist = @()
$size = @()

# Ask user for server hostname
$server = Read-Host "Let me know server to measure"

# Collect share names from the server
$sharelist = (Get-WmiObject -Class win32_share -ComputerName $server | Format-Table -HideTableHeaders Name | Out-String).trim()

# Parse the list through a text file for formatting purposes
Set-Content -Path ".list.txt" -Value $sharelist
$sharelist = Get-Content -Path ".list.txt"
Remove-Item ".list.txt"

# Concatonate hostname and sharename to an array
foreach ($item in $sharelist) {
    $share += ("\"+$server+""+$item).trim()
    }
cls

# Measure the size of each share individually and write it to a variable
foreach ($item in $share) {
    $kb = (Get-ChildItem $item -Recurse | Measure-Object -Property length -sum | Format-Table -HideTableHeaders sum | Out-String).trim()
    $mb = $kb/1MB
    $mb = "{0:N2}" -f $mb
    $size += $item+" - "+$MB+"MB"
    }
    
# Write result to a file    
add-content -Path C:PowershellShare_Enumerate_Sizesharelist.txt -Value $size

# Share_Enumerate_Size

# Define variables and arrays

$list = @()

$share = @()

$sharelist = @()

$size = @()

# Ask user for server hostname

$server = Read-Host "Let me know server to measure"

# Collect share names from the server

$sharelist = (Get-WmiObject -Class win32_share -ComputerName $server | Format-Table -HideTableHeaders Name | Out-String).trim()

# Parse the list through a text file for formatting purposes

Set-Content -Path ".list.txt" -Value $sharelist

$sharelist = Get-Content -Path ".list.txt"

Remove-Item ".list.txt"

# Concatonate hostname and sharename to an array

foreach ($item in $sharelist) {

$share += ("\"+$server+""+$item).trim()

}

cls

# Measure the size of each share individually and write it to a variable

foreach ($item in $share) {

$kb = (Get-ChildItem $item -Recurse | Measure-Object -Property length -sum | Format-Table -HideTableHeaders sum | Out-String).trim()

$mb = $kb/1MB

$mb = "{0:N2}" -f $mb

$size += $item+" - "+$MB+"MB"

}

# Write result to a file

add-content -Path C:PowershellShare_Enumerate_Sizesharelist.txt -Value $size

This script takes a long time to complete in large environments
. If anyone has tips on how to streamline the code for better performance, please add a comment 🙂

Automating best pratice for security groups in Active Directory

In order to maintain best practices in a multi domain forest, we occasionally have to create file and application access groups to secure sensitive resources we manage. Creating a 3 groups to do this is a lot of hassle, but it needs to be done, however you don’t need to do it manually.

I created a script to take care of this day to day task for me. The script basically does 3 thing:

It checks if a security group with that name already exists and if so it aborts.
It creates 3 security groups: a “Domain Local” group for rights assignment, a “Global” group to put my users in, and a “Universal” group to link the Global and Domain Local groups, as well as to link groups from other domains in our forest.
It asks the user what folder to add rights to and what rights to add (Read, Write and/or Modify) and then sets those rights on the appropriate folder.

The script uses Quest Active Roles AD Management snapin for Powershell (available here)

I’ve added logging using the transcript functionality, and if you check out line 19 and 114 you see that I’m starting and stopping logging to a specific file using the “Start-Transcript” and “Stop-Transcript” cmdlets. This means that the script will throw and error in ISE since it doesn’t support transcripting, but running it in a normal powershell windows will ensure that everything happing between line 15 to 113 get’s logged!

Without further ado, heres the script:

########################################################################################################
# This scripts creates groups based on best practise and the current naming convention at &lt;company&gt;
# 3 groups will be created, on Global for user memberships, one Universal for cross domain
# memberships and a Domain Local group for rights assignement.
#
# When executing the script, you will be asked for a group name. Only write the name of the resource
# you like to secure 
. The string "FILE_" will be added in front, and "_G", "_U" and "_DL" will be
# added to each of the 3 groups respectivly based on their type 
.
# Interlinking group memberships are added automatically, but users will need to be added to the
# group ending with "_G" (Global).
#
# No rights are assigned on resources. Assign the requested rights on the group ending with "_DL". As
# a result of the interlinking group memberships, the members of the "_G" group and groups made a
# member of the "_U" group will also gain or be denied access to the resource based on the rights
# assigned to the "_DL" group.
########################################################################################################

# Add Quest ADmanager Snapin
Start-Transcript -Path 'C:PowershellAD_File_Group_Creationaction.log'
Add-PSSnapin Quest.Activeroles.ADManagement

# Nulling out variables to avoid left over values being used in script run
$inputname = $null
$domain = $null
$name = $null
$domain = $null
$G = $null
$U = $null
$DL = $null
$counter = $null
$acl = $null
$ar = $null
$folder = $null
$rights = $null
$sign = $null

# Get information on group name and format group name to current naming convention
$folder = Read-Host 'Please type or copy in the full and correct path to the share and folder the groups will assign rights to. This will be used for the description fields and rights assignement'
$rights = Read-Host 'Enter R for Read, W for Write and/or M for Modify to rights on the target folder'
$inputname = Read-Host 'Name of security group'
$inputname = $inputname.ToUpper()
$name = "FILE_"
$name = $name+$inputname
$domain = "nordic"
$G = $name+"_G"
$U = $name+"_U"
$DL= $name+"_DL"

# Check if the group already exists
$GroupExists = Get-QADGroup $name

IF ( $GroupExists -eq $null ) {
    # Add groups
    Write-Host "Creating new groups"
    New-QADGroup -Name $G -SamAccountName $G -GroupScope 'Global' -ParentContainer 'OU=Organizational Unit,DC=domain,DC=com' -Description "Users have access to $folder"
    New-QADGroup -Name $U -SamAccountName $U -GroupScope 'Universal' -ParentContainer 'OU=Organizational Unit,DC=domain,DC=com' -Description "Users have access to $folder"
    New-QADGroup -Name $DL -SamAccountName $DL -GroupScope 'DomainLocal' -ParentContainer 'OU=Organizational Unit,DC=domain,DC=com' -Description "Users have access to $folder"
    sleep 2
    cls

    # Assign standard group memberships
    Write-Host "Assigning interlinking group memberships"
    Add-QADGroupMember $domain$DL $domain$U
    Add-QADGroupMember $domain$U $domain$G
    sleep 2

    # Add rights on the folder   

    # Read
    IF ($rights -like "*R*" ) {
        $rule = New-Object system.security.accesscontrol.filesystemaccessrule($DL,"Read","ContainerInherit,ObjectInherit","None","Allow")
        $acl = Get-Acl $folder
        $acl.AddAccessRule($rule)
        Set-Acl $folder $acl
        }

     # Write
    IF ( $rights -like "*W*" ) {
        $rule = New-Object system.security.accesscontrol.filesystemaccessrule($DL,"Write","ContainerInherit,ObjectInherit","None","Allow")
        $acl = Get-Acl $folder
        $acl.AddAccessRule($rule)
        Set-Acl $folder $acl
        }
     # Modify
    IF ( $rights -like "*M*" ) {
        $rule = New-Object system.security.accesscontrol.filesystemaccessrule($DL,"Modify","ContainerInherit,ObjectInherit","None","Allow")
        $acl = Get-Acl $folder
        $acl.AddAccessRule($rule)
        Set-Acl $folder $acl
        }
    cls
    $sign = "."
    $signs = "."
    $counter = 0
    while ( $counter -lt 10 ) {
        cls
        write-host "All done$signs"
        $signs = $sign+$signs
        $counter = $counter+1
        sleep 1
        }
    }

ELSE {
    $counter = 11
    while ( $counter -gt 0 ) {
        $counter = $counter-1
        CLS
        Write-Host "The groups beginning with" $name "already exists. Please select another group name"
        $counter
        Sleep 1
        }
    }
Stop-Transcript

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

########################################################################################################

# This scripts creates groups based on best practise and the current naming convention at <company>

# 3 groups will be created, on Global for user memberships, one Universal for cross domain

# memberships and a Domain Local group for rights assignement.

# When executing the script, you will be asked for a group name. Only write the name of the resource

# you like to secure

. The string "FILE_" will be added in front, and "_G", "_U" and "_DL" will be

# added to each of the 3 groups respectivly based on their type

# Interlinking group memberships are added automatically, but users will need to be added to the

# group ending with "_G" (Global).

# No rights are assigned on resources. Assign the requested rights on the group ending with "_DL". As

# a result of the interlinking group memberships, the members of the "_G" group and groups made a

# member of the "_U" group will also gain or be denied access to the resource based on the rights

# assigned to the "_DL" group.

########################################################################################################

# Add Quest ADmanager Snapin

Start-Transcript -Path 'C:PowershellAD_File_Group_Creationaction.log'

Add-PSSnapin Quest.Activeroles.ADManagement

# Nulling out variables to avoid left over values being used in script run

$inputname = $null

$domain = $null

$name = $null

$domain = $null

$G = $null

$U = $null

$DL = $null

$counter = $null

$acl = $null

$ar = $null

$folder = $null

$rights = $null

$sign = $null

# Get information on group name and format group name to current naming convention

$folder = Read-Host 'Please type or copy in the full and correct path to the share and folder the groups will assign rights to. This will be used for the description fields and rights assignement'

$rights = Read-Host 'Enter R for Read, W for Write and/or M for Modify to rights on the target folder'

$inputname = Read-Host 'Name of security group'

$inputname = $inputname.ToUpper()

$name = "FILE_"

$name = $name+$inputname

$domain = "nordic"

$G = $name+"_G"

$U = $name+"_U"

$DL= $name+"_DL"

# Check if the group already exists

$GroupExists = Get-QADGroup $name

IF ( $GroupExists -eq $null ) {

# Add groups

Write-Host "Creating new groups"

New-QADGroup -Name $G -SamAccountName $G -GroupScope 'Global' -ParentContainer 'OU=Organizational Unit,DC=domain,DC=com' -Description "Users have access to $folder"

New-QADGroup -Name $U -SamAccountName $U -GroupScope 'Universal' -ParentContainer 'OU=Organizational Unit,DC=domain,DC=com' -Description "Users have access to $folder"

New-QADGroup -Name $DL -SamAccountName $DL -GroupScope 'DomainLocal' -ParentContainer 'OU=Organizational Unit,DC=domain,DC=com' -Description "Users have access to $folder"

sleep 2

cls

# Assign standard group memberships

Write-Host "Assigning interlinking group memberships"

Add-QADGroupMember $domain$DL $domain$U

Add-QADGroupMember $domain$U $domain$G

sleep 2

# Add rights on the folder

# Read

IF ($rights -like "*R*" ) {

$rule = New-Object system.security.accesscontrol.filesystemaccessrule($DL,"Read","ContainerInherit,ObjectInherit","None","Allow")

$acl = Get-Acl $folder

$acl.AddAccessRule($rule)

Set-Acl $folder $acl

}

# Write

IF ( $rights -like "*W*" ) {

$rule = New-Object system.security.accesscontrol.filesystemaccessrule($DL,"Write","ContainerInherit,ObjectInherit","None","Allow")

$acl = Get-Acl $folder

$acl.AddAccessRule($rule)

Set-Acl $folder $acl

}

# Modify

IF ( $rights -like "*M*" ) {

$rule = New-Object system.security.accesscontrol.filesystemaccessrule($DL,"Modify","ContainerInherit,ObjectInherit","None","Allow")

$acl = Get-Acl $folder

$acl.AddAccessRule($rule)

Set-Acl $folder $acl

}

cls

$sign = "."

$signs = "."

$counter = 0

while ( $counter -lt 10 ) {

cls

write-host "All done$signs"

$signs = $sign+$signs

$counter = $counter+1

sleep 1

}

ELSE {

$counter = 11

while ( $counter -gt 0 ) {

$counter = $counter-1

CLS

Write-Host "The groups beginning with" $name "already exists. Please select another group name"

$counter

Sleep 1

}

Stop-Transcript

I still consider myself a novice at Powershell, however and advanced one at that, and I’d love to get feedback on better approaches to my scripting, both in the sense of optimizing the script for performance, and simplifying the script itself. I’d also be happy to answer any questions regarding the script 🙂