giving you more byte

Enabling RDP Remotely

Need remote access and forgot to turn RDP access on? Argh, how to get to that server (or workstation)? PSExec comes to the rescue in four easy steps! PsExec is a light-weight telnet-replacement that lets you execute processes on other systems, complete with full interactivity for console applications, without having to manually install client software. For those of you not familiar with Sysinternals I highly recommend you check out the suite of tools freely available from Microsoft – Download PSExec – Copy to your Windows System 32 folder. This way its always available straight up when you fire up an administrative command prompt – c:\windows\system32 Open a command line and type the following command (ensure you swap out ‘remote-machine-name’ for the hostname of your remote server): psexec \\remote-machine-name reg add "hklm\system\currentcontrolset\control\terminal server" /f /v fDenyTSConnections /t REG_DWORD /d 0<span id="mce_marker" data-mce-type="bookmark" data-mce-fragment="1">​</span> This command adds a registry entry that enables RDP connections. Still in the command line enter the following commands, again swapping out ‘remote-machine-name’ for the hostname of your remote server: psexec \\remote-machine-name netsh firewall set service remoteadmin enable psexec \\remote-machine-name netsh firewall set service remotedesktop enable<span id="mce_marker" data-mce-type="bookmark" data-mce-fragment="1">​</span> These commands set the firewall to enable remote administration and then allows remote desktop connections through the firewall. And that’s it. You should now have remote access to that server (or workstation).  

Exchange Offline Help Files

Hey Guys, here are some must have downloads and reading for you Exchange Admins. Preferred Architecture, Exchange Server 2016 Preferred Architecture Exchange Server 2013 Preferred Architecture  Download Offline Help Files, Download Exchange Server 2013 help – Download Exchange Server 2010 help – Download Exchange Server 2007 help – Download Architecture Posters, Exchange Server 2013 SP1 Architecture Poster Exchange Server 2010 Architecture Poster Exchange Server Tools Documentation This tools documentation provides detailed information about tools that can help you plan, install, manage, and troubleshoot Exchange Server. Microsoft Exchange Server Analyzer Articles Exchange Remote Connectivity Analyzer Tool Microsoft Exchange PST Capture Auto Accept Agent Deployment and Administration Guide Microsoft Exchange Server Intelligent Message Filter v2 Operations Guide Microsoft Exchange Server User Monitor Microsoft Exchange Server Quota Message Service Deploying Exchange ActiveSync Certificate-Based Authentication Microsoft Exchange ActiveSync Mobile Administration Web Tool Microsoft Exchange Server MAPI Editor Microsoft Exchange Server Stress and Performance Tool Microsoft Exchange Load Generator Microsoft Exchange Server Public Folder DAV-based Administration Tool Microsoft Exchange Server Profile Analyzer Microsoft Exchange 2007 Anti-Spam Migration Microsoft Exchange Server Jetstress 2010 Microsoft Exchange Server Jetstress 2007 Inter-Organization Replication Tool Application Analysis Envisioning Process Microsoft Application Analyzer 2006 for Lotus Domino Exchange Server 2003 Coexistence and Migration for Lotus Domino Mail Migrating from Lotus Notes to the Microsoft Collaboration Platform Exchange 2010 UM Troubleshooting Tool Exchange 2013 Management Pack Health Sets Operations Manager Management Pack for Exchange 2010 Exchange 2010 Management Pack Guide Operations Manager Management Pack for Exchange 2007    

Office 365: Planning – Network Bandwidth Tools

Microsoft has provided some great resources for you to analyse your environment and make an informed decision. Check out the Network planning and performance tuning for Office 365 article from Microsoft for further information, definitely a recommended read! Exchange Client Network Bandwidth Calculator The Exchange Client Network Bandwidth Calculator has been designed to help anyone planning an Exchange Server deployment to predict the network bandwidth requirements for a specific set of clients. Lync 2010 and 2013 Bandwidth Calculator A Microsoft Excel spreadsheet that calculates WAN bandwidth requirements for a Skype for Business Server and Lync Server deployment based on administrator-specified user profiles and network information, and a Word document user guide that accompanies the spreadsheet. OneDrive for Business Client Network Bandwidth Calculator The best method for determining bandwidth requirements when deploying OneDrive for Business is to measure the bandwidth used during a small roll out. If this is not possible, this calculator can be used to provide a loose estimate.    

[ warning] [vmusr:vmtoolsd] Failed registration of app type 2 (Signals) from plug-in unity.

An error while logging in through RDP onto a Windows Server 2008R2, a VM under ESX 5.5  – [ warning] [vmusr:vmtoolsd] Failed registration of app type 2 (Signals) from plugin unity. Here is an example of the error captured with a quick PowerShell one-liner. Get-EventLog application -InstanceId 1000 -Newest 5 | fl Index : 27823 EntryType : Warning InstanceId : 1000 Message : [ warning] [vmusr:vmtoolsd] Failed registration of app type 2 (Signals) from plugin unity. The issue here lies in that the tools.conf file failed to be created during upgrade of VMTools during a recent ESX upgrade. Strange as this error is meant to be fixed in VMTools version 9.05, and yet this is the installed version. No matter, easily rectified. Open your favourite text editor (tell me your in the comments). Open your favourite text editor (tell me your in the comments). Copy and paste the text from below into the newly created text file. [logging] log = true     # Enable tools service logging to vmware.log vmsvc.level = debug vmsvc.handler = vmx   # Enable new "vmusr" service logging to vmware.log vmusr.level = error vmusr.handler = vmx # Enable "Volume Shadow Copy" service logging to vmware.log vmvss.level = debug vmvss.handler = vmx  Save your new text file as tools.conf, see the table below for the location of the file. Restart the VMTools service and you should be good to go 😉    

Exchange “Send As” Permissions

Ok, someone asked me the other day how to allow a user to send email as if they were the owner of another mailbox. This can be done by granting the user Send-AS permissions said mailbox – or you can even grant rights to send as a distribution group, very handy for members of a team. #Grant user Jane Doe permission to send from John Doe's mailbox: Add-ADPermission - Identity "Jane Doe" ` mailboxesAdd-ADPermission cmdlet-User "John Doe" ` -ExtendedRights Send-As One thing to note here is that Add-ADPermission cmdlet uses -Identity to classify the user who is assigned the permissions. You cannot use the mailbox alias for the -Identity and must use a unique display name or the distinguished name. #Same as before but this time we know the display name is not unique so we are going to use the distinguished name: Get-Mailbox janed | Add-ADPermission -User johnd -ExtendedRights Send-As Nice and easy. The process is the same for adding permission to a distribution group. #Grant user Jane Doe permission to send from Sales mailbox: Add-ADPermission - Identity Sales -ExtendedRights Send-As -User janed #Grant user Jane Doe permission to send from ALL distribution groups: Get-DistributionGroup -ResultSize Unlimited | Add-ADPermission -User janed -ExtendedRights Send-As And lets say Jane changes roles and no longer needs to send on behalf of John… #Remove user Jane Doe permission to send from John Doe's mailbox: Remove-ADPermission - Identity "Jane Doe" ` mailboxesAdd-ADPermission cmdlet-User "John Doe" ` -ExtendedRights Send-As    

Why, Mr Hacker (Bot)?

This entry follows a serious attempt to once again compromise the site. This is to you Mr Hacker (Bot)?: Why bother? If  you simply asked I would give you access. This site has no information that is not given freely regardless and has been created and maintained for sharing information. Just ask, mate. In the meantime, each IP is logged and reported to the appropriate ISP.    

Add SIP Address to Match Primary SMTP

Hi All Here is a little snippet to add a SIP address to a users mailbox so that it matches the users PrimarySmtpAddress. $mbxes = Get-Mailbox ForEach ($mbx in $mbxes) { # SET THE newSIP ADDRESS VARIABLE TO MATCH THE PRIMARY SMTP ADDRESS: $newSIP = 'SIP:' + $($mbx.PrimarySmtpAddress) Write-Host "Adding $newSip to" $mbx.SamAccountName # ADD THE newSIP ADDRESS TO THE MAILBOX: Set-Mailbox -Identity $mbx.SamAccountName -EmailAddresses @{Add = $newSip} } Change the $mbxes variable to suit your needs and run. Worked like a charm 🙂

Purge a Directory Synchronised Office 365 Account and Resynchronise without Removing from AD

To purge and resynchronise an AD synchronised with DirSync account from Office 365, follow these steps: 1.    Fire up Windows Azure Active Directory for Windows PowerShell (Check out managing Office 365 through Azure PowerShell here). 2.    Run the following command to connect to online service, remembering substitute our friend Fakey McFakerson for your own admin credentials. # CONNECT TO MICROSOFT ONLINE SERVICE (SUBSTITUTE ADMIN CREDENTIALS AS APPROPIATE): $cred = Get-Credential -Credential [email protected] Connect-MsolService –Credential $cred 3.    Now, we need to grab the user Object ID. Once you obtained it copy and paste it elsewhere as you’ll need it later. # OBTAIN THE USER'S OBJECT ID (SUBSTITUTE THE UPN AS APPROPIATE): Get-MsolUser -UserPrincipalName [email protected] | fl *objectID* 4.    Ok, now that we have the user Object ID we can remove the account. # REMOVE THE USER ACCOUNT (SUBSTITUTE THE UPN AS APPROPIATE): Remove-MsolUser -UserPrincipalName [email protected] 5.    With the account removed, we now need to purge the account from the Office 365 Recycle Bin. This is where we use the Object ID obtained earlier. Run the following command to purge the user from recycle bin.   # PURGE THE ACCOUNT FROM THE RECYCLE BIN (COPY AND PASTE THE OBJECT ID IN PLACE OF THE 'X's): Remove-MsolUser -ObjectId xxxx-xxxx-xxxx-xxxx –RemoveFromRecycleBin With the user(s) accounts purged from Office 365 you need to perform the Directory Synchronisation (unless you are happy to wait for it to sync on the next run? Default is every three hours). 6.   To force immediate directory synchronization, type the following into a run window on the Directory Synchronisation server: C:Program FilesMicrosoft Online Directory SyncDirSyncConfigShell.psc1 This opens up a PowerShell window with the appropriate synchronisation commands pre-loaded.…

Read more

Deleting Folders and Files with PowerShell

Ok, so you are running out of space on that drive and need to clean up. Of course you could jump into the GUI and manually select the files and folders but that is just so labour intensive. Fire up PowerShell and I’ll walk you through the Remove-Item cmdlet. Check out the TechNet article here: The Remove-Item cmdlet does exactly what it says on the tin. It deletes one or more items and because it is supported by many providers, it can delete many different types of items, including files, directories, registry keys, variables, aliases, and functions. Use “Get-Help Remove-Item –Full” for a full description of the cmdlet and the associated switches. You’ll notice that there are a number of Aliases associated with the cmdlet that we can utilise to save our fingers. If you just want some examples to show you what to do use “Get-Help Remove-Item –Examples”. ALIASES: ri, rm, rmdir, del, erase, rd So, instead of typing “Remove-Item deleteMe.txt” to delete the text file “deleteMe.txt” in the current working directory, we can just use one of the aliases and shorten the command to “ri deleteMe.txt”. Cool, huh. Use which ever alias makes sense to you. I tend to use “del” personally… Ok, let’s have a look at some examples. EXAMPLE 1: Remove all files from C:DeleteMeFolder. It is important to note that the use of the period (.) will not delete directories or files with no extension. Remove-Item C:DeleteMeFolder*.*   EXAMPLE 2: Remove all word documents from the current directory BUT not any documents with “keepMe” in the filename that does not include “1”. The current directory…

Read more