Microsoft

How to Install Windows PowerShell

by Jason Green on April 2, 2013 · 0 comments

If you want to know how to install Windows Powershell, this is the article you must read. You can run commands or scripts on your server using this software. Windows Powershell has been added to Windows Server 2003 but it is included in Windows Server 2008 R2 as well. System administrators and IT professionals will be able to automate many tasks using Windows Powershell in their servers. Scripting will be enhanced as well. In Internet there are a lot of places to download this software.

If you are looking for detailed instructions to help you install windows powershell for SQL 2008 R2, check out the page below for all of the downloads and details.
http://www.businesshut.com/microsoft/install-windows-powershell-for-sql-2008-r2/

In a Core server PowerShell is really useful. After installing the operating system you need to install PowerShell. This way you will enjoy a powerful programming language when you need to configure some parameters of your operating system. Let me tell you something. If know how to install Windows Powershell and have this computer program in your server, getting rid of a virus is only an annoyance. If you want to protect your server to avoid that virus kick in, then you need to use Windows PowerShell.

In the next lines we are going to talk about how to install Windows Powershell in a short time. You will know all the tips you need to install this useful programming language to take full advantage of all the capabilities of your server.

First, you have to go to the Windows Management Framework Core section in the website of Microsoft. Get a free download of Windows Powershell and choose your operating systems. Second, access the location where you will download the “setup.exe” file and start off downloading. After the installation click Start, All Programs, Accessories and select Windows PowerShell. You need to install this computer program in your server right away. If you want to use PowerShell V2.0 you need to install Windows Server 2002 Service Pack 2 (SP2) as well. In the next lines we will talk about commands used to install it, important considerations to do it and many other things.

The first thing you need to do when you follow the steps above is to get the Windows Management Framework. Now you just have to lunch the program. To do this just click Start-Run and type “powershell”, then press Enter and you are done. When you do this, Windows PowerShell will be added to the programs that your frequently use. If you do not see this program in this section, you can create an icon manually. Please make sure that WMI and remote management are enabled in your server. Then you will need to click Start, then Run and find “services.msc”. The following programs must be set to run automatically: Windows Remote Management (WS-Management) and Windows Management Instrumentation. As you can see, knowing how to install Windows Powershell is very easy.

Now you need to test the program trying a connection to the 2003 machine. You do it when you open PowerShell in a Windows 2003 Server. Then run the command “Enable-psRemonting” and press ENTER. If you are using a Windows 2008 R2 machine, you really need to use this command while you are there. Now we are going to use the following command for our first connection Enter-psSession MachineName and this one to end our remote section Exit-psSession .

You have learned how to install Windows Powershell using the tips we have told you. As you can see, understanding how to install Windows Powershell is not rocket science. All you need to do is to follow the tips above and that is all. You have learned that after downloading the software from the Microsoft website you need to choose the operating system. Please make sure you select the correct operating system because if you do not do it, the software will not run properly.

We told you that you need to use the command section and type the commands we told you above. Please remember that you need to use this file: services.msc. This is an important step as well. We have outlined all the steps you need to know on how to install Windows Powershell but you can also watch a video in Youtube to improve the process. You can also get the help of an IT professional if you go to any programming forum on the Internet.

The Basics of Windows Scripts

by Jason Green on March 26, 2013 · 0 comments

Windows scripts are used to control all the aspects of Windows. They are created using a powerful scripting language that this operating system has built-in. The basics of Windows scripts for Windows XP are what we will talk about here. You must also know that Windows 98 was the first operating system of Microsoft with scripting included. If you want to finish your job easier and faster you need to create Windows scripts. You will just need to use your computer to get this help. As you have experienced, computers are one of the most helpful devices invented by the human mind. But if you want to finish your tasks in the computer in the shortest time possible you need Windows scripts.

In the next lines we are going to talk about what you can do using Windows scripts. We will talk about variables, importance of scripts, OCR, comments, how to create your first script and many other interesting things.

There are many Windows applications to automate all your tasks. You can use standard programming paradigms to go beyond step repetition. You will also find many of them with OCR techniques included. This way you will recognize the most difficult words. Your Windows scripts can be run via schedule with the use of the Task Scheduler. This computer program is included in every copy of Windows.

We just need to launch the Notepad to start off creating Windows scripts. These are the names of other editors you can use: SciTE, Scintilla and Script Editor. But most of the time Notepad will be enough. When you finish writing the script you need to give it the .VBS extension.

If you want to write out your first script, please open your Notepad and type the following line: wscript.echo “Hello World” and that is all. If you double click on the file a pop up will show up with “Hello World” in it. But you can also use the command prompt and type “cscript hello.vbs” as well.

If you are a programmer, you will need to comment your programs if you want to know what they are all about in the future. A comment will not be seen by anyone but you. Your program will not be affected in any way if you write comments. Others will know what a piece of code is all about if you comment on it. To write a comment in a VBS file you just need to type REM at the beginning of the line and start off writing in the same line your comment. If an error happens, Windows will let you know about it. It will also let you know about the line that has the error.

All Windows scripts use variables to store strings and values. All you need to do to give a value to a variable is to type its name followed by the = sign. For example, ‘store = 24′ will be fine. The variable “store” holds the value “24” in the previous example. To create input boxes you will use the following command: InputBox(“message”). For example, store = InputBox(“What is your store?”) will display an input box asking for a store name. The value of the input box will be stored in the variable “store”.

If you want to really speed up your tasks you need to get the help of a computer. Windows scripts are here to make your dream come true. You can automate almost anything in Windows and this is thanks to the help of Windows scripts. As you have seen in the above lines, creating a script in windows is not rocket science. If you want to automate Windows using scheduled task you need to use the Task Scheduler.

You must also remember that you need to comment almost all the pieces of your scripts. The reason is that if anyone will ever need to modify your script, he/she will know what your program is all about if you leave comments on it as we said above. This is a very easy task and you will avoid a lot of problems in the future. Windows scripts are here to stay because your productivity will be enhanced using them. You need to automate most of your tasks and Windows scripts, the Task Scheduler and many other tools will help you a lot.

What is Windows PowerShell?

by Jason Green on March 19, 2013 · 0 comments

This should give a very high-level of what Windows PowerShell is for anyone who really just doesn’t know what PowerShell is all about.

Overview

Windows PowerShell is used by System Administrators who write in a task based scripting and command line language system. IT System Administrators use this scripting language to automate the administration of Windows Operating Systems, as well as other applications that are run on Windows. This system also allows IT Administrators to be able to use commands to manage all of the computers in a network from the command line.

Features

PowerShell offers many features that will simplify a System Administrators job. One feature the program provides is by having a navigation system that is based on commands, which lets the Administrator browse through a computers’ registry database, as well as any other data storage areas. The way the program is designed is to use a common syntax and naming system, so data between computers can be shared easily.

Complex Tasks

When using this program for completing complex and tedious tasks, System Administrators are able to use a combination of simple command tools in the program in order to complete tasks, instead of issuing the commands out separately. This system houses over one hundred different commands to use; or the user may create their own commands, and then share them among other power users.

Data Accessibility

With Powershell, a System Administrator is able to access their computer file system. The shell system is also able to give the administrator access to other computers data storage areas and registries just as easily.

New Language

When using the Powershell system, the user of the system will realize that it does not use any other existing shell system languages. The reason why this system has its own language is because it needs to manage the .NET Framework objects. The shell system had to have an advanced system when dealing with the higher level programming systems, such as C#.

Using Commands

A System Administrator is able to use command line programs inside of the shell system. The system is also able to start a graphics interface which can run a program like Notepad at the shell prompt. When using the Powershell commands, a power user is able to use the select-string feature to change Windows Programs text.

Processing Objects

When a System Administrator is using Powershell, they are essentially using the framework for .NET objects. This new language system will enable an Administrator to be able to think in objects. A user can think of an object as a data entity that has different properties, which are similar to what characteristics are. When working with objects of the same type and properties, they will often have different values for each of the properties.

Windows Powershell is able to simplify the way a System Administrator runs commands. They will be able to access data storage areas from different computers as easily as they can open a file on their own computer. This system also simplifies the way to enter commands in programs by combining the tools in order to complete a task.

Windows PowerShell Overview

by Jason Green on February 2, 2013 · 0 comments

You need a Windows PowerShell overview now. But first we need to tell you that PowerShell is a framework that automates tasks. It comes integrated with the .NET framework. It is made up of an associated scripting language and a command-line shell. You will be able to do administrative tasks in remote and local Windows systems. Powershell gives you full access to WMI and COM.

In the next lines of this Windows PowerShell overview you will know many interesting things about this computer program. We will talk about Powershell V2 and its features, cmdlets, embedding Powershell in management applications, scripting, pipelines and more. You can consider this article as a Windows PowerShell short review because we are going to talk about many cool features of PowerShell.

In this Windows PowerShell overview we must tell you that you can execute four types of commands here: cmdlets, scripts, functions and executable programs. PowerShell.exe will launch an executable program in a separate process. A PowerShell process will execute a cmdlet. The output of the commands will be displayed in a command line interface. Here you will enter the commands as well. You will not find syntax highlighting in PowerShell but it comes with a Win32 console in its user interface with customizable tab completion built-in.

PowerShell translates into invocations of the original commands the creation of aliases by cmdlets. You can use positional and named parameters for commands. The parameters of external executables will be passed via the argv variable array to be parsed by the executable. For cmdlets, PowerShell itself will bind the argument to the value.

Cmdlets are used in Powershell to implement specific functions. They are specialized commands indeed. When Powershell needs to instantiate and invoke .NET classes it uses the help of cmdlets. “Modules” is the name of a more portable version of Cmdlets added in PowerShell V2. PowerShell also implements a pipeline like Unix and Linux. A pipeline will take the output of a cmdlet to another cmdlet.

As you can see, this Windows PowerShell overview has many interesting things. Now we are going to talk about scripting. Windows PowerShell uses cmdlets imperatively to implement complex operations using a dynamically typed scripting language. This scripting language support .NET integration, functions, branching, variables, loops, error/exception handling and closures/lambda expressions. Binary prefix notations are supported by the Windows PowerShell scripting language as well.

You can embed PowerShell in a management application to implement the management functionally using its runtime. If you want to use this feature you need to use its managed hosting API. The process of the application will be run using a “runspace”. You must also create a pipeline if you want to run a command.

Microsoft has released PowerShell V2 with Windows 7 and Windows 2008 R2. With this new version of PowerShell you can run scripts and cmdlets on a remote machine. You can also invoke a pipeline or script asynchronously. Transactional operations are allowed with the help of cmdlet as well. Using the scripting language of PowerShell you can create cmdlets.

In the above lines we have been talking about many things in this Windows PowerShell overview. One of the most important things about this computer program is that you can execute many types of files. This way you will have more room to maneuver in your programming tasks. You need to initiate .NET classes when you use cmdlets. Using a dynamically typed scripting language you can use cmdlets imperatively as we have told you in the above lines. When you create aliases using cmdlets, PowerShell will translate them into invocations of the original command.

This Windows PowerShell overview is important because you will have more things to implement when you know about the features of this software. Windows 7 and Windows 2008 R2 were released with PowerShell included. You can do an awesome job in remote server using PowerShell V2 and cmdlets. They will help you perform transactional operations. You have learned a lot of things in this Windows PowerShell overview. Cmdlets, PowerShell V2, types of commands allowed and many other things have been explained. The managed hosting API is another really cool feature that you can take advantage of right away as well.

Install Windows PowerShell for SQL 2008 R2

by Jason Green on January 3, 2011 · 21 comments

I was recently installing SQL Server Management Studio Express 2008 R2 and the installation failed temporarily because Windows PowerShell wasn’t installed. There wasn’t a link, so I thought a quick search would get me the file on Microsoft’s website. I was wrong. I found plenty of documentation and getting started guides for Windows PowerShell, but no installation downloads.

It was frustrating, but I finally found the PowerShell installation file. I thought I’d share the link here to help everyone find this file a little faster. (And so I can find it easily in the future.)

If the links below don’t work, you should have enough detail here to refine and shorten your search.

Windows PowerShell 1.0 English Language Installation Packages for Windows Server 2003 and for Windows XP

Microsoft KB Article / Location of PowerShell Downloads: http://support.microsoft.com/?kbid=926139

After some additional searching, I found the homepage for Windows PowerShell. You should be able to find everything you need there.
http://technet.microsoft.com/en-us/scriptcenter/dd742419.aspx

You can also get Windows PowerShell 2.0 included with Windows Management Framework here:
http://support.microsoft.com/kb/968929

Microsoft Gatineau – Google Analytics Killer?

by Jason Green on August 27, 2010 · 1 comment

Is Microsoft Gatineau ready to strip Google Analytics of the web analytics throne?

I’ve been using both Microsoft Gatineau and Google Analytics on one of my sites for about 3 months. I think that’s plenty of time for me to give a fair analysis of both packages.

*Note that I am much more experienced with Google Analytics, so that might have some effect on my opinion. However, I’m trying to be as neutral as possible in this review.

1. User Interface / Usability:
Winner: Google Analytics
Why?: Google is king when it comes to user interfaces. (Not starting off so neutral, are we?) When I log into my Google Analytics account, I’m presented with a very useful dashboard. If the information I need isn’t there by default, I can easily add it. On the other hand, Microsoft’s Gatineau gives me a 3-layer calendar that allows me to select a date range by day, week, or month, with a single click. This might be useful if jumping from one date range to another was a frequent activity, but so far, it’s not. This date-range picker takes up 4 inches above the fold on EVERY report! The two inches below that is a description of the report you’re viewing, and below that is the graph for the report you chose. Unfortunately, half of it is below the fold!

Navigation through reports is done through a folder structure.

This isn’t awful, but getting to the next level always requires 2 clicks. One to select the item and display the menu, and another to choose between demographics or diving a level deeper.

2. Useful Information
Winner:Google Analytics
Why?: This would be a tie because they both have all standard web analytics information, except Microsoft makes it so much harder to view the useful information. Sorry to go back to usability, but with the GA dashboard, I can view my most useful information on one screen. With Gatineau, it takes 12 to 20 clicks and 6-10 page loads just to get the same information.

3. Demographics
Winner: Microsoft Gatineau
Why?: Because Google doesn’t have it. However, with this being Gatineau’s claim to fame, I’m unimpressed. Over the past 3 months, I only have demographics information on about 20% of my visitors. Sure this information is useful for some things, but with 80% being unknown, I really don’t know much more than I did before.

Overall Winner: Google Analytics!

Who didn’t see that coming?

I was really hoping to write some good things about Microsoft Gatineau, but until they improve the user interface, I won’t be leaving Google Analytics any time soon. Also note that Gatineau hasn’t been officially released yet. There are some features which haven’t even been activated, such as the emailing or exporting of reports. However, the framework of what’s to come is there, and I have to say, it’s no Google-killer.

I’d love to hear from other Gatineau users. Is there anyone out there that would choose Gatineau over Google Analytics?

Even though GA won this battle, I’d still encourage you try out Microsoft Gatineau and Google Analytics to decide for yourself.

I look forward to your comments.

- Jason Green