View and reset Terminal Server session on Microsoft Servers via Command Line

07/27/2007


For the administrators that love use command line option;   
 

When you manage multiple server with terminal server service, is possible to view active MS RDP session and reset the specific session via command line, at this pourpose there are two great commands that you need to remmeber:  

 

QUSER (for view local and remote session) below all the option possible:

 RESET SESSION (for reset local and remote session) below all the option possible:

 

 

 

 Example:   

C:>quser /SERVER:SRV1.caloni.net   

 USERNAME              SESSIONNAME        ID  STATE   IDLE TIME  LOGON TIME   

 administrator          rdp-tcp#219        29  Active          .  27/07/2007 14.4    

reset session /SERVER:SRV1.caloni.net  29

 

 

 

 

command,line,terminal,service

Managing Exchange 2007 using PowerGUI (Part 2)

07/26/2007

I would to thaks Henrik Walther that has write this article for MSExchange.org
---------------------------------------------------------------------
Advanced management features in PowerGUI.

If you missed the first part in this article series please read Managing Exchange 2007 using PowerGUI (Part 1)

In part 1 of this article series covering the PowerGUI tool, I gave you an introduction to the feature-set in the PowerGUI tool as well as showed you how easy it is to manage Exchange Server 2007 objects in bulk. In part 2 of this article series, I will continue where we left by moving on to a couple of what could be considered advanced topics. I will show you how to create additional Exchange 2007 nodes in the PowerGUI navigation tree, as well as how to manage public folders, provision mailbox users, create reports and so forth.

Creating Additional Exchange 2007 Nodes in the Navigation Tree

Although the navigation tree only shows a few Exchange Server 2007 specific nodes by default, you can easily add additional nodes as required. As shown in Figure 2.1, this is done by right-clicking on the folder or node under which you want to create a new node.


Figure 2.1:
Creating additional Nodes in the navigation tree

This will open a New Node window, where you first need to type in the name of the new node. Next we need to specify the cmdlet used to perform the action required. When done, click OK to have the new node created.

For example, if we wanted to create a node that listed all Exchange 2007 Mailbox servers in the organization we would create a node similar to the one shown in Figure 2.2.


Figure 2.2: Specifying the name and cmdlet of the new node

Managing Public Folders

Another great thing about PowerGUI is that it allows you to manage public folders in an easy and efficient way. I bet those of you who already tried managing public folders from the Exchange Management Shell (EMS) are pretty frustrated right? Okay okay, I know you can manage public folders stored in an Exchange 2007 public folder database using the Exchange 2003 System Manager, but unfortunately not all of us have the option of keeping an old Exchange 2003 server in the organization just for the purpose of managing public folders.

As you can see in the PowerGUI console, there is a Public Folders node in the navigation tree. Let us click on this node. As you can see only the IPM_SUBTREE is listed here. Now let us click Subfolders under Links in the Action pane. This will list all subsfolders as shown in Figure 2.3. Currently two public folders exist here; Budgets and Marketing.


Figure 2.3: Listing Public Folders

Creating a new public folder is a straightforward task, you simply click New Folder in the Action pane and then specify the name for the public folder followed by clicking OK.

Using the tasks under Links in the Action pane, we can have client and administrative permissions listed as well as see statistics for the folders.


Figure 2.4:
Listing Public Folder Client Permissions

For example, what if you wanted to mail-enable a public folder? Well although no action for this specific task exists in the Action pane, we can easily create it. To do so click Add new item under the Actions, then specify a name for the task (such as Mail-Enable), then type in the cmdlet used to mail-enable a public folder (which is Enable-MailPublicFolder), then click OK.

Note:
It is not expected that you know all these cmdlets off the top of your head, you can instead search for them using the search field to the right of the command field.


Figure 2.5: Creating a Mail-Enable Public Folder item in the Action pane

Now just select the public folder(s) that should be mail-enabled, and then click the new Mail-Enable task in the Action pane, then click Ok. To verify that the public folder(s) have been mail-enabled, expand the Recipients folder in the navigation tree - select Mail-Enabled Public folders and there you have it.

Provisioning Users

PowerGUI also gives you the option of provisioning mailbox users, which means that you can, for example, create 50 new mailbox users in a matter of a few minutes.

To provision for users using PowerGUI you first have to export at least one existing mailbox user to a .CSV file. To create the .CSV file select the respective mailbox user(s), then click Report as CSV in the Action pane. In the Report as CSV windows, specify the path for the CSV file as shown in Figure 2.6 then click OK.


Figure 2.6: Specifying the path for the mailbox user CSV file

A Notepad file containing the selected users will now be opened (Figure 2.7). After having edited this file as needed, save and close it.

Note:
In order to provision for mailbox users successfully, the .CSV file created must contain at least the following columns: UserPrincipalName, Name, Database and OrganizationalUnit, Password otherwise the import will fail.


Figure 2.7: List of Mailbox users to be provisioned

Now in order to provision for the new mailbox users, click Create from CSV file in the Action pane, then specify the path to the CSV file you previously created and click OK.


Figure 2.8: Importing the CSV file

You have now provisioned the new mailbox users specified in the CSV file (Figure 2.9).


Figure 2.9: List of New Mailbox Users

Reporting

PowerGUI also gives us the option of creating reports with all kinds of information in them. For example, we could create a report that includes a list of all Mailbox users and their associated mailbox limit. We could also make a report of all the different Exchange 2007 servers in the organization etc. The cool thing about the reporting feature is that you can export it directly to an HTML file besides XML and CSV files.

To create an HTML report simply select the objects in PowerGUI, then click Report as HTML in the Action pane. Figure 2.10 below shows us a simple list of the Mailbox users in the organization.


Figure 2.10:
Basic Mailbox User Report

Conclusion

Throughout this article series, I have shown you how, with the help of PowerGUI, it is possible to manage mailbox users, public folders and other Exchange server objects in bulk. In addition, you have seen how to provision mailbox users, and create reports etc. Needless to say, we have only touched the surface of what is possible with PowerGUI, but I hope you got an understanding of how powerful this tool actually is. In addition it is worthwhile to note that PowerGUI can also be used to manage all other types of objects. Currently you can use PowerGUI to manage systems based on Windows PowerShell technology. At the time of writing, these include Windows XP/Vista, Windows Server 2003/2008, Operations Manager 2007, SQL, networking and other new systems from Microsoft, but keep an eye on http://www.powergui.org as there constantly are new PowerPacks uploaded to library.

That was all for this time, I hope you enjoyed the reading…

If you don't have read Managing Exchange 2007 using PowerGUI (Part 1) click HERE!

Exchange,2007,Power,GUI

Managing Exchange 2007 using PowerGUI (Part 1)

07/26/2007

I would to thaks Henrik Walther that has write this article for MSExchange.org
-------------------------------------------------------------------------
How to manage Exchange Server 2007 objects in bulk using a freeware tool called PowerGUI.

If you would like to read the next part in this article series please go to Managing Exchange 2007 using PowerGUI (Part 2)

Introduction

In Exchange Server 2007, management of single recipients, databases, servers and other objects can typically be performed from within the Exchange Management Console, but when you are required to perform bulk changes of one or more of these objects, you need to turn to the new Exchange Management Shell (EMS). Although the Exchange Product group did everything in their power to make managing tasks via the EMS as easy, simple, and painless as possible, Exchange administrators with no scripting experience at all can find it extremely difficult to manage objects using this new command shell. Because a lot of work went into creating consistent verb-noun pairs (aka cmdlet’s), most Exchange administrators don’t have a problem issuing single cmdlet’s such as Move-Mailbox or Get-MailboxDatabase, but as soon as it comes to using piping (meaning one cmdlet makes use of the output of another cmdlet) or simply modifying objects in bulk, most Exchange administrators get stuck.

In addition to the above, the frustrated Exchange administrators have to use the EMS to manage public folders, POP3/IMAP4 access and many other Exchange 2007 features until Exchange Server 2007 Service Pack 1 RTWs.

So what can you do to begin mastering the Exchange 2007 cmdlets? Well this is where PowerGUI comes into the picture. PowerGUI is a freeware tool developed by Dmitry Sotnikov who’s a CTO in the Windows Management group at Quest Software. PowerGUI is an extensible graphical administrative console, which you can use to manage systems based on Windows PowerShell technology. At the time of this writing this includes Windows XP/Vista, Windows Server 2003/2008, Operations Manager 2007 and other new systems from Microsoft. As I’ll show you throughout this articles series, PowerGUI allows you to use the rich capabilities of Windows PowerShell in a familiar and intuitive GUI console.

Alrighty, we have covered enough background information now let’s get started…

Installing PowerGUI

First thing we want to do is to download the latest version of PowerGUI (which at the time of this writing is version 1.0.6 beta) from the PowerGUI.org site. Then we simply launch the PowerGUI.msi package in order to begin the installation process. On the first page, click Next as shown in Figure 1.1.

In this article series, we’ll install PowerGUI directly on an Exchange 2007 server, but you could also install the tool on another server or Windows XP client with the Windows 2003 AdminPak and Exchange 2007 System Management tools installed.


Figure 1.1: PowerGUI Installation Wizard – Welcome Page

Now accept the license agreement and click Next once again. This brings us to the User Information page, which you should fill out and then click Next.

On the Select Features page, we can select which PowerPacks we want to install. As you can see in Figure 1.2, the PowerPack for Exchange 2007 is selected by default, so we can just click Next.


Figure 1.2: PowerGUI – Selecting Features to be installed

All necessary information has now been collected by the Installation Wizard, and we can click Next in order to let the actual installation to begin. When the installation has completed, click Finish as shown in Figure 1.3.


Figure 1.3: Completing the PowerGUI Installation

Using PowerGUI to Manage Exchange Server 2007

With PowerGUI installed, we can launch the application by clicking Start > All Programs > PowerGUI (Figure 1.4).


Figure 1.4: Launching PowerGUI

When PowerGUI has been launched you’ll see a screen similar to the one in Figure 1.5. This is the main console from where we, in this case, can manage Exchange Server 2007 objects.


Figure 1.5: PowerGUI Main Console

As you can see, the PowerGUI console looks very similar to a traditional MMC, it has a navigation tree, a work pane and an action pane as you’ll see in a moment.

Managing Mailbox Users

The first thing I wanted to show you is how you can manage mailbox users in bulk. To see a list of all mailbox users, click the Mailboxes object under the Recipients container. This will give us a list of all mailbox user objects (Figure 1.6), where the Name of the user, Alias, ServerName, and ProhibitSendQuota are the mailbox properties that are listed by default.


Figure 1.6: Listing Mailbox User Objects

If you want to have additional mailbox properties listed, you can right click on one of the columns, then choose the respective mailbox properties on the context menu as shown in Figure 1.7 below.


Figure 1.7: Selecting Mailbox Properties

Clicking More will reveal a complete list with all properties that are available for a mailbox-enabled user object (Figure 1.8).


Figure 1.8: List of additional Mailbox Properties

Let’s switch back to the main PowerGUI console again. As you could see back in Figure 1.6, the Prohibit Send Quota for my mailbox is set to 5GB (5000000KB). Let’s try to set this same quota for the rest of the mailbox recipients (which are all currently set to unlimited). To do so, we first need to select each of the users by holding down CTRL while clicking on each of them, or by clicking CRTL+A to select all, then de-select the mailbox already configured with this limit. When the respective mailbox recipients have been selected, click Change Properties in the Action Pane. This will bring up the Change Properties Parameters window shown in Figure 1.9. Here we need to scroll down to the ProhibitSendQuota property, and then specify the new value followed by clicking OK.


Figure 1.9: Changing ProhibitSendQuota for selected Mailbox Users

That was pretty easy right?

Exposed Cmdlet Code

Just like is the case with the wizards in the Exchange Management Console, you have the option of seeing the exact PowerShell commands used to perform specific tasks. This is done by clicking the PowerShell Code tab in bottom of the work pane (Figure 1.10). This gives you the option of reusing the code in a custom PowerShell script etc.


Figure 1.10: Exposed PowerShell Code

Search Filters

PowerGUI also gives you the option of filtering objects in a similar way as to how filtering works within the Exchange Management Console (you can even create multiple filters) by clicking the Filters in the top of the work pane as shown in Figure 1.11.


Figure 1.11: Using Search Filters

That was it for part 1 of this article series covering the PowerGUI tool, but you can look forward to part 2 which will be published in a near future. Until then have a nice one!

If you would like to read the next part in this article series please go to Managing Exchange 2007 using PowerGUI (Part 2)

Network Access Protection (NAP) for Windows Server 2008

07/26/2007

Microsoft TechNet Radio

Welcome to Microsoft TechNet Radio. TechNet Radio is an internet radio show with content for IT professionals. TechNet Radio features the latest information from Microsoft insiders and industry luminaries, as well as profiles of leading companies. We'll bring you the trends and technologies that are shaping our industry, and offer perspectives from your peers. Look for new episodes of TechNet Radio every week.

Listen to TechNet Radio

July 17, 2007

Network Access Protection (NAP) for Windows Server 2008

On today's TechNet Radio, Michael Murphy discusses Network Access Protection or NAP in Windows Server 2008 with Amith Krishnan. With NAP, you can create customized health policies to validate computer health before allowing access or communication, to automatically update compliant computers to ensure ongoing compliance, and, optionally, to confine noncompliant computers to a restricted network until they become compliant. Amith Krishnan is a Senior Product Manager at Microsoft, and is responsible for the product management of Windows Server's platform networking and security technologies.

Length: 0:19:36

WMA | MP3 High | MP3 Low
To save to your computer, right click and choose 'save target as…'.

NAP,Windows,server,2008

List of updates in Windows Server 2003 Service Pack 2

07/26/2007

SUMMARY

This article lists problems that are fixed in Microsoft Windows Server 2003 Service Pack 2 (SP2). Service packs are cumulative. This means that the problems that are fixed in a service pack are also fixed in later service packs.

Windows2003,SP2

Keep an Eye on Your Servers with Operations Manager 2007

07/26/2007

System Center Operations Manager 2007 offers a great leap forward in the Microsoft operations management platform. Operations Manager 2007 represents a paradigm shift in strategy, moving from computer-focused monitoring to a true service-oriented

monitoring platform. While the new model bears some resemblance to its predecessor as an agent-based monitoring solution, carrying forward concepts familiar to any Microsoft® Operations Manager (MOM) 2005 administrator, much has changed. As you'll see, there are exciting new features, new management interfaces, and lots of additional resources for learning more about this latest addition to the Microsoft System Center Family.


Management Interfaces

In no place are the changes more apparent than in the new management interfaces. Gone are the separate Operations and Administrator consoles, and in their place is a consolidated Operations Console that delivers administrative, authoring, operational, and reporting functions (see Figure 1). Also gone is the single, often confusing folder tree of the MOM 2005 Administrator Console. An interface that looks much like Outlook® takes its place, exposing five function-specific workspaces: monitoring, authoring, reporting, administration, and my workspace.

Figure 1 Operations Console
Figure 1 Operations Console (Click the image for a larger view)

The monitoring workspace exposes alert, state, performance, and diagram views of the network infrastructure in a clean interface, similar to what you'd see in the Operator Console in MOM 2005.

The Authoring workspace is where you configure new rules and create groups on which rules and monitors will operate. A dramatically improved reporting interface is integrated into the Operations Console, eliminating the need to visit a separate reporting Web site. An interface for executing administrative tasks, such as computer and network device discovery and configuration of security and notification settings, is also included. Finally, My Workspace allows users to create custom views, save frequently used views and searches, and configure custom alert notification subscriptions.

The Operations Console is loaded with context-sensitive help, including links to product documentation, online webcasts, and conceptual guidance. The Operations Console also includes rich search functionality, allowing users to define advanced search criteria for any object type, returning results based on object type and value characteristics defined in the search.

The Actions pane in the Operations Console offers a host of context-sensitive tasks that provide information on object configuration and state, and it allows you to launch the new Health Explorer for the targeted object (see Figure 2). In Health Explorer, the tree structure representing the health of the monitored objects for a given entity (monitored object) is hierarchical. Every entity is monitored on at least four parameters: Availability, Configuration, Performance and Security. These values cascade up; the state of each of these parameters is calculated based on the state of monitors that reside underneath it in the hierarchy.

Figure 2 Health Explorer
Figure 2 Health Explorer (Click the image for a larger view)

Health Explorer diagnoses failures on monitored objects and gives you the ability to act on error conditions by clicking hyperlinks within the event detail. You also run any diagnostic or recovery task appearing in the details pane of the Health Explorer (as in Figure 3) on demand, or configure the task to run automatically when an alert is generated. The output of any diagnostic task (such as retrieving a list of running processes) will be displayed automatically in the details pane when the state change event is highlighted.

Read complete article at Microsoft Link!

Operation,Manager,2007

In Windows Server 2003 SP2, the "Remove" button for the service pack is not available in the "Add or Remove Programs" item in Control Panel

07/26/2007

SYMPTOMS

After you install Microsoft Windows Server 2003 Service Pack 2 (SP2), the Remove button for the service pack is not available in the Add or Remove Programs item in Control Panel.

 

CAUSE

This problem occurs if the previous service pack was installed by using the SETUP /n command. For example, this problem may occur if Windows Server 2003 Service Pack 1 (SP1) was installed by using this command.

Note The /n switch installs the service pack without creating a backup folder. You must have this backup folder to remove the service pack by using the Add or Remove Programs item in Control Panel. We recommend that you always create a backup folder when you install a service pack.

WORKAROUND

To work around this problem, remove the service pack by running the Spuninst.exe utility. The Spuninst.exe utility is located in the following folder:
%SystemRoot%$NTServicepackUninstall$

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


 

This Article was published By Microsoft and you can view it at this link