'Virtual keys' are designed to be used when installing products that require activation in virtualized environments or on a hypervisor layer. The virtual key will allow you to change most virtual hardware configurations - such as memory or CPU - without requiring re-activation and will allow you to move instances of the product from one virtual environment to another without requiring re-activation. 

 

For products like Windows Server 2008, Small Business Server 2008, two keys are provided. Both are 25 character keys. One is for installing the operating system in the physical operating system environment, and the other is for installing the operating system in a virtualized operating system environment.

Explore several new features for authentication and authorization in Microsoft Office SharePoint Server (MOSS) 2007 and Windows SharePoint Services 3.0 that make it easier to develop and deploy solutions in Internet-facing and extranet environments. Here is the useful content from MSDN:

 

http://msdn.microsoft.com/en-us/library/bb975136.aspx
Introduction to Forms Authentication in SharePoint Products and Technologies
Deciding to Use Forms Authentication
Reviewing a Typical Scenario for Authentication
Reviewing Changes to Authentication Terminology
Setting Up Forms Authentication
Granting Permissions to Create My Sites

 

http://msdn.microsoft.com/en-us/library/bb975135.aspx
Developing Custom Membership and Role Providers
Applying the XML File for the Data Source
Inheriting from the Membership and Role Base Classes
Minimum Interfaces Required by MOSS and Windows SharePoint Services
Registering the Custom Provider
Debugging the Custom Provider
Writing a Custom Forms Logon Page
Using Web Services with a Site Protected by Forms Authentication

 

http://msdn.microsoft.com/en-us/library/bb977430.aspx
Introduction to Differences Between Forms Authentication and Windows Authentication
Crawling Content
Integrating with the 2007 Microsoft Office System
Opening Documents in Internet Explorer
Checking the "Sign me in automatically" Check Box at Logon
Using an HttpModule During Authentication
User Profile Imports
Resolving Names
Using an LDAP Provider
Using the Microsoft Single Sign-On Service
Conclusion

 

Do we really have to know XML coding to create an application defination for SharePoint Business Data Catalog? Here is the GUI tool can do it without coding XML. 

BDC Meta Man is the first Business Data Catalog tool for all SharePoint Developers and Administrators interested in line of business data integration with SharePoint. Without writing a single line of code you can be viewing and searching across your business data through Microsoft Office SharePoint Server 2007 in minutes.

To download a trial copy click here http://www.lightningtools.com/bdc-meta-man/default.aspx

 

So, what is the applicaiton defination? An application definition describes a database or web service. It includes connection settings, authentication mode, definitions of available entities, and other information. After you upload an application definition to the Business Data Catalog, you can use its entities in lists, web parts, search, user profiles and custom applications.

In Hyper-V, UNDO is not an available option on the virtual disk menu anymore, you now have snapshots. If you want the ability to protect your VHD from any changes getting merged you need to do this.

Before you first power on a VM (the same point you would have enabled UNDO in Virtual Server), take a snapshot and call it something like UNDO DISCARD. This just makes your VHD effectively read only and all changes are written to a working AVHD file.

Power on your VM and work away.  When you want to effectively “Turn OFF and Discard” all changes, then apply revert (under action menu) to the UNDO DISCARD snapshot and it is all gone…start a new test scenario. Just remember that if you made any changes to the VM settings, they are also discarded.