The New Service Pack is expected to be available for Technet, MSDN, and Volume Licensing customers on February 17th, with a release to the General public about a week later. Of course these dates can move around a bit. The product was Released to Manufacturing on February 9th.
How much difference will you see after you install this Service Pack?
For most people there won’t be any notable change to what you are doing or any fantastic new features. Unless you do quite a bit with Virtualization, most of this service pack is about compiling the hotfixes and patches. If you look at the notable changes document you will find that the majority of changes revolve around some services that are not used by most people (Direct Access, Failover Clustering, etc…)
For those of you using Hyper-V or VDI, there are some really nice new features. Primarily Dynamic Memory in Hyper-V which will allow a much greater density of Virtual Machines on each server. Microsoft says around a 40% improvement of density per server. RemoteFX is the other big feature which will allow you to Virtualize the GPU on a server to the Virtual Desktop. Giving a much richer desktop experience to client machines, especially the very low cost, very thin client devices.
Starting with Windows Vista and being improved in Windows 7 is the new search capabilities. Searching for content in your computer has never been quicker than it is now.
With the indexing service it is very simple and fairly quick to not only search for a file name but to search the contents of documents and email.
Microsoft builds in filters for many of the common file types (doc, docx, xls, xlsx, txt, etc…) however some third party software has files that are not indexed by default.
PDF files are a very common file that is used that is not indexed by default. You must install Acrobat reader or some other viewer, which will register the PDF extension with the system and start indexing the files.
If you are running the 32 bit version of Windows Adobe Acrobat Reader 9 will automatically install the ifilter program which will allow the system to not only index the file name but also index the contents of PDF files that are recognized as text. Some PDF files recognize the contents as text and other while showing words see them as a picture. Usually this can depend on how the file was created. If you take a Word doc and save as a PDF, Acrobat can recognize the characters. If you scan a document Acrobat will usually see this as a picture of the paper, you can run OCR software to covert to characters.
Continue reading »
The Remote Desktop Connection Manager (or RDCMan, for short) is a pretty cool, free tool from Microsoft to help manage all those remote desktop connections.
You can download the tool here
You can create multiple files with an .rdg extension.
Once you have created a file you can look at the settings.
The settings will allow you to manage logins, gateways, display settings, and other options for all of your connections.
Now just add your servers into the system. You can create groups for them and override the default settings with different connections options.
Once you have the servers added, you can see a preview of each one and just double click on one to connect to it. Switching to another server is as easy as clicking on that one.
Instead of having a bunch of windows open, you can manage all of the connections very easily with this free tool. Give it a try.
PowerShell is this awesome tool that Microsoft is integrating to just about everything. Back to the command line we go. Scripting is really powerful and can really streamline a lot of processes.
One of most common questions I get is, “How do I run a script in PowerShell?”
This might seem really simple until you actually go a run a script.
In the following screen shot I am trying to run the script getver.ps1 which is in the directory ‘c:\temp\scripts’. Since PowerShell looks similar to the command shell you would think that you could just type the name of the script. When you do you get the first response. In PowerShell you have to type the whole path of the script, or if you are in the directory already you can use ‘.\scriptname to call the script. However, you will notice that that doesn’t work either.
Before you can run a script you have to set the execution policy. There are 4 levels.
- Restricted – No scripts can be run. Windows PowerShell can be used only in interactive mode.
- AllSigned – Only scripts signed by a trusted publisher can be run.
- RemoteSigned – Downloaded scripts must be signed by a trusted publisher before they can be run.
- Unrestricted – No restrictions; all Windows PowerShell scripts can be run
The default is Restricted. You can set your policy to AllSigned or RemoteSigned which works great in your environment to distribute scripts. If you are just testing and developing scripts you may want to use Unrestricted on that workstation. For a more information on script signing check out this article http://technet.microsoft.com/en-us/magazine/2008.04.powershell.aspx
As you can see I set the execution policy to Unrestricted and then ran the script. The script does run at this point at returns the version of the OS that is running.
Hopefully, this will help get those scripts running.
