In Microsoft Exchange 2010 there was a very easy and powerfull tool, message tracking viewer. With this graphical tool you could track any message within your Exchange organization.
With Exchange 2013, the message tracking is not graphical anymore. So it’s not that easy to track some messages. The new way to go is Windows PowerShell! With the following example, you can easy create a overview of all the messages in your Exchange environment.
When you’ve configured mailbox quota’s within your Exchange 2010/2013 environment, you’ve to check the configuration sometimes. Using Microsoft PowerShell, you can watch the current configuration within a few second, so this is extremely powerfull!! But, when you have to query for some specific user or result, it’s not that easy.
There’s a very usefull command within PowerShell that I’m using almost for all my scripts….Out-GridView. When using the parameter Out-GridView, the results are not showing within the PowerShell screen, but in a separate window! Within this window, you can very easy add some search criteria….for example: specific user, quota or an overview per database.
One requirement is that the Windows Feature “Windows PowerShell Integrated Scripting Environment (ISE)” is installed on the Exchange servers or mangement server from where you’re running the commands.
1.) Open the Exchange Management Shell (EMS)
2.) For an overview of the current mailbox quota, use the following command.
Get-Mailbox -Identity mswinkels | ft Name, IssueWarningQuota, ProhibitSendQuota, ProhibitSendReceiveQuota
3.) The results of this command is shown within the PowerShell window
4.) Now we’re running the same command, but replace “ft” (format-table) with “select” and add the parameter “Out-GridView”
Get-Mailbox -Identity mswinkels | Select Name, IssueWarningQuota, ProhibitSendQuota, ProhibitSendReceiveQuota | Out-GridView
5.) Now the results are in a separate window! Extreme usefull when you’ve have to search for a specific result or results.
Today I’ve upgraded Mozilla Firefox from version 35.0.1 to 38.0.5. After the succesfully upgrade, everythin looks fine. But there’s one crucial thing that has been changed in version 38.x. The “Options” menu is not a pane anymore, but it will be open in a new tab. I’ve customized some things in the browser (hide the network button) in the UserChrome.css file. In the new Options tab, the netwerk button is available again for my users. So, I want to hide this option and it works great in version 35.x.
With a simple edit in the UserPref.js file within the profile of my users, I can force the “Options” menu view in the ‘old’ way. After that, the network button is gone again!!
I’ve used RES Workspace Manager 2014 for distribution the new UserPref.js file to all of my users, but you can also use some other 3th party software or do it just manually.
1.) Open Mozilla Firefox 38.x
2.) Type about:config
3.) Search for “browser.preferences.inc”
4.) Set the option “Browser.preferences.inContent” from true to false
5.) Close Mozilla Firefox and open it again
Microsoft has released a new version of Microsoft Server 2016 Technical Preview 2, so I’ve installed this version immediately within my Hyper-V environment. After starting the setup, you’ll see there’re two versions:
Windows Server Technical Preview 2
Windows Server Technical Preview 2 (with local admin tools)
The difference between theese two versions is the User Experience. In previous version of Windows, it was called Windows Server Core Edition. So the version without the local admin tools, the user has no option to enable/install the graphical user interface (GUI).
After the installation, you’ll see that there’s a difference between the User Experience. One version, the Server Manager is available and the other version has only a command prompt available. You’ve to manage this server from another server with the Remote Server Administrative Tools (RSAT). The version with the admin tools included, there’s a possibility to enable the Graphical User Interface (GUI).
After a reboot, the server is turned on with a Graphical User Interface (GUI) and it looks pretty cool!! And YESSSS, the start menu is back again What a great time for some users!! With this new version of Windows Server, there’s is a complete new “world of bits and bytes”….
Microsoft has released a great free Ebook of how to Deploy Hyper-V with Software-Defined Storage & Networking (SDN). In this Ebook you’ll learn all the basics of Software Defined Datacenter and how to use it in real life!
During a deployment of Microsoft Windows 8/8.1, you’ll receive a question to select a prefered network connection. This is also happening during a task sequence within Microsoft SCCM 2012 R2. It’s easy to disable this
question during the task sequence, using an unattend XML file.
1.) First open the “Windows System Image Manager”, also known as WSIM
2.) Select the image you want to deploy. In my example “Install.WIM” from the Windows 8.1 source files
3.) Create a new catalog for this image
4.) After the catalog has succesfully created, create a “New Answer File”
5.) Navigate to the following selection
6.) Select the “+” on the left side and naviagte to “OOBE”
7.) Right-click on “OOBE” and select “Add Settings to Pass7oobeSystem
8.) Select in the right pane OOBE
9.) Select in the properties pane “HideWirelessSetupInOOBE” and set the value to “True”
10.) Save the XML file on your “source” directory on your primary site server
11.) Create a new package with the source directory to the directory you’ve created in the stap before
12.) Do NOT create any program in the package, so select “Do not create a program”
13.) Distribute the new package to your distribution point(s)
14.) Open your task sequence and navigate to stap “Apply Operating System”
15.) Select the option “Use an unattended or Sysprep answer file for a custom installation
16.) Select the package you’ve created before and type the name of your XML file within that package source location
17.) Boot a client from the network (PXE) and select the task sequence.
If you follow the steps within the task sequence, you’ll see that you didn’t receive a network connection screen anymore.