Category: XP

I be talking about Windows 7 at the TPCUG MEETING

at the Trumbull Library Community Room

33 Quality Street, Trumbull, CT on Thursday night May 21, 2009 at 7pm come join us.

A Privacy breach is an unauthorized disclosure of personal confidential information that violates state or federal privacy laws.  In the event of a privacy breach, the following procedures should be followed to ensure the appropriate level of response

To understand data breaches we first need to see how bad it is.

To see a Chronology of Data Breaches by year go here

To see the law by each state go here.

Do you ever get a document in a different langue that you do not understand get Windows Live Translator !

It works for both Office 2003 and Office 2007 !, just download the installer here.

Here are some details for both Office versions:

Office 2007: http://blogs.msdn.com/translation/archive/2008/08/06/office-document-translation.aspx

Office 2003: http://blogs.msdn.com/translation/archive/2008/08/11/office-2003-setup-instructions.aspx

Once you’ve thoroughly researched and planned your implementation of Failover clusters, you’re ready to actually create the cluster. The mechanism to create and manage Failover clusters is the Cluster Administrator application, part of the Administrative Tools folder.
To create a new Failover cluster, follow these steps.
(Note that the first three steps must be performed on all nodes that will be part of the Failover cluster.)

Tips RSS Feed

Subscribe to the TechNet Magazine Tips RSS feed.

1. Open Windows Server 2008 Server Manager from the Administrative Tools folder.
2. Select Features in the left pane and click Add Features in the right pane.
3. Select Failover Clustering in the left pane and click Next.
4. Open Failover Cluster Management from the Administrative Tools folder. In the center pane, click Validate A Configuration from the Management section.
5. On the first screen of the Validate A Configuration Wizard, enter the network name of each node. You should select all of the nodes that are available to ensure that your testing validation is as accurate as possible.
6. Click Next to show the Testing Options page. You should run all tests to ensure that you fully test your configuration. If you are running the validation process of failing a previous validation, you can run only the tests that were not successful earlier.
7. Click Next to verify the tests to be performed. Once the tests are completed, the Summary page will indicate whether the tests were successful and whether the configuration is suitable to use as a Failover cluster.
8. Click Finish to end the Validate A Configuration Wizard. If errors were reported, fix the problems indicated and run the wizard again. If the validation was successful, click Create A Cluster in the Failover Cluster Management window.
9. Once the Create Cluster Wizard starts, you need to enter the names of the nodes that will be used to form the cluster. These should be the same nodes you entered previously during the validation process.
10. Click Next to proceed to the Access Point For Administering The Cluster page. On this page you need to enter the cluster name and IP address that will be used to identify and administer the cluster once it is created. The cluster name and IP address will be the virtual name registered in DNS and will be used to connect and manage the cluster itself. This information is usually different than the name and IP address that will be used by clients to connect to clustered applications.
11. Click Next to validate the settings and proceed to the Confirmation page. Ensure that all the information is accurate for the creation of the cluster. If not, click Previous to go back and change the settings. Otherwise, click Next to proceed to the cluster creation page.
At the completion of the cluster creation process, the Summary page will show you the results. If there were no errors, your cluster was successfully formed. If there were any errors, click the View Report button to get details.
12. Click Finish to exit the wizard.

From the Microsoft Press book Windows Server 2008 Administrator’s Companion by Charlie Russel and Sharon Crawford.

I get asked all the time how do I get on a beta.

The answer is first go to Connect.Microsoft.com

Sign in using  a Microsoft Live account, then click on the connection directory and choose the Beta that interests you. You will need to apply and once accepted you NEED to give feedback to the beta group

One area to Join is the

Microsoft Game Studios Beta Program

On Your Dashboard

Adding…

We want EVERYONE – not just hardcore players! Whether you play once a year or every day, whether you pre-order the latest consoles or wouldn’t think of paying for a game – we want feedback from you!

The will  be a Beta call in June for a preview, some chance that were talked about include – REVISION control in PowerPoint !!!

More use of the ribbon bars.

Cannot wait to see the product.

Server2008  7 RC now you can download it

Welcome to Server2008 r2 Release Candidate (RC) testing. If you like trying out pre-release software, now’s your chance. You get to see what’s coming, and we get to see if our changes and fixes from the Beta testing are working correctly.

How do you test the software? You put it on your PC, and then do what you’d normally do. Your PC will automatically and anonymously send our engineers the information they need to verify the fixes and changes they made based on the Server2008 r2 Beta tests.

You don’t need to rush to get the RC. The RC will be available at least through July 2009 and we’re not limiting the number of product keys, so you have plenty of time.

Here with the Microsoft Power 4.

SQL Server, Webcast, Virtual Labs, and Visual Studio

Knocked off WebCast off his feet, with a great magic trick!

Windows PowerShell™ is a command-line shell and scripting language designed especially for system administration. Built on the Microsoft .NET Framework, Windows PowerShell helps IT professionals control and automate the administration of Windows operating systems and of applications that run on Windows.

The simple command tools in Windows PowerShell, called cmdlets, let you manage the computers in your enterprise from the command line. Windows PowerShell providers let you access data stores, such as the registry and the certificate store, as easily as you access the file system. In addition, Windows PowerShell has full support for all Windows Management Instrumentation (WMI) classes.

Windows PowerShell is fully extensible. You can write your own cmdlets, providers, functions, and scripts, and you can package them in modules to share with other users.

Windows® 7 includes Windows PowerShell 2.0. It also includes other cmdlets, providers, and tools that you can add to Windows PowerShell so that you can use and manage other Windows technologies such as Active Directory® Domain Services, Windows® BitLocker™ Drive Encryption, the DHCP Server service, Group Policy, Remote Desktop Services, and Windows Server Backup.

What’s new in Windows PowerShell?

The following changes are available in Windows PowerShell in Windows 7:

• New cmdlets. Windows PowerShell includes more than 100 new cmdlets, including Get-Hotfix, Send-MailMessage, Get-ComputerRestorePoint, New-WebServiceProxy, Debug-Process, Add-Computer, Rename-Computer, Reset-ComputerMachinePassword, and Get-Random.
• Remote management. You can run commands on one computer or hundreds of computers with a single command. You can establish an interactive session with a single computer. And, you can establish a session that can receive remote commands from multiple computers.
• Windows PowerShell Integrated Scripting Environment (ISE). Windows PowerShell ISE is a graphical user interface for Windows PowerShell that lets you run commands, and write, edit, run, test, and debug scripts in the same window. It offers up to eight independent execution environments and includes a built-in debugger, multiline editing, selective execution, syntax colors, line and column numbers, and context-sensitive Help.
• Background jobs. With Windows PowerShell background jobs, you can run commands asynchronously and "in the background" so you can continue to work in your session. You can run background jobs on a local or remote computer, and you can store the results locally or remotely.
• Debugger. The Windows PowerShell debugger can help you debug functions and scripts. You can set and remove breakpoints, step through code, check the values of variables, and display a call-stack trace.
• Modules. Windows PowerShell modules let you organize your Windows PowerShell scripts and functions into independent, self-contained units. You can package your cmdlets, providers, scripts, functions, and other files into modules that you can distribute to other users. Modules are easier for users to install and use than Windows PowerShell snap-ins. Modules can include any type of file, including audio files, images, Help files, and icons. Modules run in a separate session to avoid name conflicts.
• Transactions. Windows PowerShell now supports transactions, which let you manage a set of commands as a logical unit. A transaction can be committed, or it can be completely undone so that the affected data is not changed by the transaction.
• Events. Windows PowerShell includes a new event infrastructure that lets you create events, subscribe to system and application events, and then listen, forward, and act on the events synchronously and asynchronously.
• Advanced functions. Advanced functions behave just like cmdlets, but they are written in the Windows PowerShell scripting language instead of in C#.
• Script internationalization. Scripts and functions can display messages and Help text to users in multiple languages.
• Online Help. In addition to Help at the command line, the Get-Help cmdlet has a new Online parameter that opens a complete and updated version of each Help topic on Microsoft TechNet.

Two new types of service accounts are available in Windows Server® 2008 R2 and Windows® 7—the managed service account and the virtual account. The managed service account is designed to provide crucial applications such as SQL Server and IIS with the isolation of their own domain accounts, while eliminating the need for an administrator to manually administer the service principal name (SPN) and credentials for these accounts. Virtual accounts in Windows Server 2008 R2 and Windows 7 are "managed local accounts" that can use a computer’s credentials to access network resources