Reputation
608
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
2 7 23
Newest
 Yearling
Impact
~116k people reached

Jun
15
awarded  Yearling
Jun
12
answered Run a command on a remote Windows Server as user
Jun
12
reviewed Reviewed Run a command on a remote Windows Server as user
Jun
12
comment Missing something when adding AD users with powershell
This works nicely, but isn't required--you can still manually specify the UPN if you want to.
Jun
12
comment Does Windows 8.1 Pro have CAL included?
Short answer: No, the CAL is not included. On a related note, having a license for Outlook does not provide a CAL for Exchange Server. CALs are always purchased separately from the server license and the client license. Maddening stuff.
Jun
12
comment Remove drive given by gpo
Are you talking about mapping their home directory with a GPO? That's going to require steps that are different than if you are simply talking about a generic mapped drive.
Jun
12
answered I’m unable to get GPO Security Filtering to work for users
Jun
8
awarded  Custodian
Jun
8
reviewed Reviewed How to “jail” a ftp user inside its home directory (proftpd)?
Jun
8
reviewed Reviewed Debian Samba share Authentification with RADIUS server
Jun
8
reviewed Reviewed Installing Server 2012R2 on VM with GPT harddrive issues
Jun
8
reviewed Reviewed Certificate common name invalid
Jun
8
comment Exchange 2010 PowerShell: Value.ToMB() Method Fails Remotely but Works Locally
Footnote: based on the original answer, I finally tried running the command Get-MailboxStatistics).TotalItemSize.Value.GetType().Fullname and Get-MailboxStatistics).TotalItemSize|Get-Member on both sets of servers. With the EMC installed, this returns Microsoft.Exchange.Data.ByteQuantifiedSize as the type and lists Value as a method. Without the EMC installed, this returns the type as a String and no Value method.
Jun
8
accepted Exchange 2010 PowerShell: Value.ToMB() Method Fails Remotely but Works Locally
Jun
8
comment Exchange 2010 PowerShell: Value.ToMB() Method Fails Remotely but Works Locally
SUCCESSFUL TEST: I installed Exchange management tools on 2 management servers in the Exchange resource forest and the .Value.ToMb() method worked on both. FINAL FAILED TEST: I tried using the Value.ToMb() method from a different server in the same forest, but without the Exchange management tools installed. The statement failed again, with the Value method returning a Null expression. CONCLUSION: It looks like the EMT is required in order for the Value method to work properly against the TotalItemSize property of a mailbox statistic.
Jun
8
comment Exchange 2010 PowerShell: Value.ToMB() Method Fails Remotely but Works Locally
Tested, and unfortunately failed at a slightly different point. In this test, the Value method worked on the Exchange server, but not on a remote management machine in a different forest.
Jun
8
comment Exchange 2010 PowerShell: Value.ToMB() Method Fails Remotely but Works Locally
Note, the EWS Managed API appears to require a 64-bit machine. I ran it first from my workstation and got a Windows Installer error stating that "This installation package is not suported by this processory type. Contact your product vendor."
Jun
8
comment Exchange 2010 PowerShell: Value.ToMB() Method Fails Remotely but Works Locally
That is a factor, but I don't think the actual problem. As noted in the answer/comments from Trondh, I am unable to install the required management tools because the management machine in question is not in the Exchange forest. In this case, the Set-ADServerSettings -ViewEntireForest command does not help. Thanks, though!
May
27
comment Active Directory Claims based Authentication error in SharePoint
Truth! I feel your pain. :-/
May
21
comment Exchange 2010 PowerShell: Value.ToMB() Method Fails Remotely but Works Locally
What does this parameter do?