The first steps needed to move from an environment running an Open Source mail solution and clients in a workgroup to Active Directory and Exchange Server 2007.
With the introduction of Windows Server 2008, there is a lot more work that has to be done at the command line. While I consider this to be an unfortunate situation in general, I can whine all I want but I don't think things are going to change, so we're all going to have to get used to it. One of the side effects of command line management is having to enter long strings of command line options and the typos that ensure. Perhaps even more challenging than typos is just trying to remember the long strings with all the switches and values. I'm sure you've seen it at many demos — the TechNet presenter has a collection of text files on his desktop that he uses to copy and paste the command line argument. These guys use the product everyday in their demos and even they can't remember all the PowerShell and other commands. Well, there's nothing I can do to help you with your memory, and there's nothing I can do to help your fingers not make typos, but there is something that I can do to help you copying and pasting text into files that you'll use to help with your 169 character PowerShell command. That tool is called PureText 2.0. You can use PureText to copy just the text from a Web page or document that contains that long command line string into a text file and it removes the formatting that might make the command not work. In addition, it adds a keyboard shortcut (WINDOWS+V) to paste the pure text into your text file. This is really helpful when you need to copy that interminable string of PowerShell characters from the Exchange Server Help file into a text file. While not
A look at the Get-MailboxStatistics Exchange Management Shell cmdlet and how to manipulate its output in various ways.
A step-by-step guide on how to use Data Protection Manager (DPM) 2007 to back up Exchange Server 2007.
How to generate Active Directory accounts from a Mailbox Database using Exchange Server 2000/2003.
How to use the ServerManagercmd.exe Windows 2008 command line utility to add and remove Server Roles.
Microsoft Press just released the definitive reference for how to deploy, configure, and troubleshoot Microsoft® Office Communications Server 2007. This resource comes complete with expert insights direct from the Microsoft Office Communications Server Team. This official Microsoft RESOURCE KIT delivers insights by in the field expert consultants with in-depth technical guidance on architecture, deployment, security, administration, performance tuning, and troubleshooting Office Communications Server 2007. You'll also discover the essential information for working with VOIP and phone integration features. In addition, you get more than 150 timesaving PowerShell scripts, tools, and other job aids for automating administration, plus a fully searchable version of the entire RESOURCE KIT book.
Read more at source:http://communicationsserverteam.com/archive/2008/01/25/81.aspx
Technorati : OCS 2007, Technical Resource Del.icio.us : OCS 2007, Technical Resource Ice Rocket : OCS 2007, Technical Resource
How you can create custom management consoles in Exchange Server 2007.
The transition from Exchange Server 2003 organizations to Exchange Server 2007 is straightforward and in general not a big risk. Since there is no in-place upgrade method, it is always possible to move one step back.
Powerful combination allows PowerShell users to edit and debug scripts, then distribute these scripts to computers and servers in the network
TORONTO, CANADA – January 8, 2008 — Special Operations Software, www.specopssoft.com, a global leader of Group Policy and Windows PowerShell based Systems Management and Security software, today announced the integration of Quest PowerGUI(TM) from Quest Software with Specops Command(TM) from Special Operations Software. The integration makes it possible to use the powerful and free PowerShell script editor, Quest PowerGUI, directly from Specops Command and thus provide features like IntelliSense (to access descriptions of functions) and debugging capabilities when editing PowerShell scripts.
"The incredible synergy created by integrating Specops Command and Quest PowerGUI into a single powerful solution is very exciting," said Dmitry Sotnikov, New Product Research Manager at Quest Software. "Giving users the ability to invoke PowerGUI Script Editor to edit and debug their scripts and then use Specops Command to distribute the script to computers in the network makes perfect sense."
"The combined power and ease of use of Specops Command and Quest PowerGUI will forever change the landscape of distributed Windows-based computer management and will make Windows PowerShell the number one solution used everywhere — not only for administering a small number of servers, but tens of thousands of computers at a time," said Thorbjörn Sjövold, CTO of Special Operations Software. "Also, by simply using the free Quest PowerGUI with the free version of Specops Command, Logon and Startup scripts as we know them today will never be the same."
For more information and to download Specops Command, please visit: http://www.specopssoft.com/powershell/
