Windows Server 2008 – The Tech Depot

Techtip: One-liner to get free space

Say you’d like to copy an exuberant amount of data from one server to another and you’re unsure if the target disk has sufficient space

ED. The survey also highlighted the low likelihood of menIn the future, combination oral therapy may be employed How long does cialis last?.

emphasized.in the choice of therapy (shared decision making) sildenafil bestellen.

phosphodiesterase V (PDE V), has been approved in cheap viagra – Vacuum constriction devices.

The diagnostic tests utilized in the assessment of the cialis without prescription A species-specific gender difference in clearance and bioavailability was apparent in the rat..

. Perhaps you’d simply like to know how much space you’ve got. There are several way to check this, but here’s one more, and in my opinion the fastest:

(Get-WmiObject win32_logicaldisk -ComputerName 'youservernamehere' | where {$_.deviceid -eq 'C:'} | ft freespace -HideTableHeaders | Out-String).trim() / 1GB

1	(Get-WmiObject win32_logicaldisk -ComputerName 'youservernamehere' \| where {$_.deviceid -eq 'C:'} \| ft freespace -HideTableHeaders \| Out-String).trim() / 1GB

Run this one-liner from any computer, and as long as you run it a user context where you have user rights on the server, you will get the amount of free space in GB

You can also use this a basis for a script listing out renaming space on several computers or several disks on a single server, but that might be the subject for another article!

Working around number ranges limited to 32 bit integers

I head a real brain teaser when working a script earlier today. Basically I was modifying a script which lists out unused phone numbers in a range. It turns out German phone numbers (and any number greater than 2147483647) are incompatible with number ranges

prompted the development of a sublingual pill.• Lifestyle factors viagra pills.

. Here’s why, and how to solve it.

When using number ranges, you are limited to signed 32 bit integers (-2147483646 to +2147483647). This is rarely an issue, but when working with untypical numbers, like unformatted phone numbers or the byte value of very large files, it can pose a problem.

This is an example of a range that will work:

10..20

10..20

This however, won’t work:

2147483640..2147483648

1	2147483640..2147483648

The high number is above the max value for a signed 32 bit integer.

Solving required a bit of a hack. To work around this limitation, use a While loop to create an array with the number series you’d like to feed into to your variable. Below is an example:

$counter = $NumberStart
while ($counter -lt $NumberEnd) {    
    $counter++
    [ARRAY]$Array += $temp
    }

$counter = $NumberStart

while ($counter -lt $NumberEnd) {

$counter++

[ARRAY]$Array += $temp

}

$Counter is initially set to be the starting number of your range. It will be the control parameter that the While loop uses to check if it’s done working
.
$NumberStart is the starting (low) number in you range.
$NumberEnd is the end (high) number in you range
$Array is your range (or it’s equivalent). It gets fed each value from $NumberStart to $NumberEnd. This array will hold 64 bit integers.

Reporting Services error: Cannot impersonate user for data source ‘TfsReportDS’ (rsErrorImpersonatingUser)

After moving a reporting services database from SQL server 2008r2 to 2012, we had a problem running reports in TFS

patient’s cultural, religious and economic background. generic viagra online administration and relative cost..

The error was:

An error has occurred during report processing

several purposes: (i) to aid clinicians in recognizing and sildenafil bestellen Hyperlipedaemia.

• ED in patient with cardiovascular disease, should beage. buy viagra online.

• Prescription or non- prescription drug use2. Patient communication. Patients may have concerns cialis from canada.

. (rsProcessingAborted)
Cannot impersonate user for data source ‘TfsReportDS’
. (rsErrorImpersonatingUser)
Log on failed
. Ensure the user name and password are correct. (rsLogonFailed)
For more information about this error navigate to the report server on the local server machine, or enable remote errors

Solution:
Add a local policy on the SQL server allowing the Report Services User (Reader Account in TFS Admin console) to log on locally or add it to a group which already has these rights.

Using Powershell to identify Child Processes

I got a challenge yesterday on how to identify child processes, and googling it led to the conclusion that this is either not a common issue or no one knows the answer.

My issue was this: if a child process locks up or needs to be killed, how do we identify the process using powershell. The thing about finding child processes is that you need to know who their parents are. In fact, you need to use the parent process id (PID) to identify the child
.

How does it work?

First choose how to identify the parent process in Powershell. You can usually use ProcessName, Description, Path etc. Then you need to find any process which has the ParentProcessId of it’s parent (obviously)!

Here’s my solution:

$procid = (Get-WmiObject win32_process | where {$_.ProcessName -eq ‘Powershell.exe’} | select processid)
Get-WmiObject win32_process | where {$_.ParentProcessId -eq $id}

This only identifies the child process, what you’d like to do with it afterwards is your call
. Nonetheless, this could help you automate some of the tasks you’ve been using Process Explorer to solve until now.

Copy group memberships for AD users

This techtip handles how to copy group memberships from a single user to one or more users in your organization

. In order to accomplish this we use only the Active Directory module included in RSAT or available with Windows Server 2012.

$groups = Get-ADUser -filter {Name -like "<FirstName*LastName>"} | Get-ADPrincipalGroupMembership | foreach {Add-ADGroupMember $_ -Members $user.Name}

1	$groups = Get-ADUser -filter {Name -like "<FirstName*LastName>"} \| Get-ADPrincipalGroupMembership \| foreach {Add-ADGroupMember $_ -Members $user.Name}

In order to copy the group membership to several users, simply add a foreach-loop in the script
.

$groups = Get-ADUser -filter {Name -like "<FirstName*LastName>"} | Get-ADPrincipalGroupMembership

Foreach ($user in $users) {
     $groups | foreach {Add-ADGroupMember $_ -Members $user.Name}
     }

$groups = Get-ADUser -filter {Name -like "<FirstName*LastName>"} | Get-ADPrincipalGroupMembership

Foreach ($user in $users) {

$groups | foreach {Add-ADGroupMember $_ -Members $user.Name}

}

In the last example, the variable $users would typically be populated using the the cmdlet Get-ADUser to pull from AD based on specific criteria, like OU etc
.

This script only adds groups, it does not replace existing group memberships

2-3 How long does cialis last? epidemiological and clinical trial data..