A temporary user profile is issued each time an error condition prevents the user's profile from loading. Temporary profiles are deleted at the end of each session, and changes made by the user to their desktop settings and files are lost when the user logs off.  On a Vista client computer, you may encounter profile issues if you log on with a user in the Guests group. This article will discuss this problem.

When you log on to a computer installed with Vista, you may encounter the following behavior:

•      User profile being deleted on log off

•      Desktop icons, files and other profile related items being not saved

•      Getting a temporary profile each time you logon to either the standalone computer or domain

For instance, Right click on Computer and Select Properties, Select Advanced system settings under Control Panel > System, Under User Profiles select Settings, The Status for the profile will be Temporary

The prime reason of why this would happen is because the user is part of the local Guests or "Domain Guests" group. This affects administrators as well.

What we should do? Remove the user in question from the local Guests or "Domain guests" group and that should do it.

For local users:

1.    Click Start

2.    Right click Computer and Select Manage

3.    Select Local Users and Groups > Groups

4.    Double click Guests

5.    Check if the user that is having the issue is a member of the Guests group

6.    If so, remove the user from the Guests group

7.    Log off the workstation and log back on

8.    Verify the profile is now local

If the issue is happening on multiple machines for the same user in a domain, check the Domain Guests group:

1.    Open “Active Directory Users and Computers” (dsa.msc)

2.    Select the Users container

3.    Double click “Domain Guests”

4.    Select the Members tab

5.    Check if the user that is having the issue is a member of the Domain Guests group

6.    Repeated steps 2-5 with the "Guests" group

If the problem still exists and the user is not a member of the Guests or Domain Guests group, verify the user is not a member of a group which is a member of the Guests or Domain Guests groups. Furthermore, if the user is not member or not nested to be a member of Guests or Domain Guests, mostly, the original profile is corrupted, and please engage administrator to check.

Do you want to deploy Office 2007 in your organization? If so, the Office Deployment Guide below is a must read article before you plan any such deployment.

This guide provides instruction for the Computer Imaging System and Application Management feature teams to install the 2007 Office system on the disk image, and then deploy that disk image throughout the organization. In addition to describing how to customize the 2007 Office system, this guide provides an alternative scenario for organizations that have already deployed Windows Vista but have not yet deployed the 2007 Office system. This guide will also outline the tasks each team must complete to upgrade existing Microsoft Office XP and Microsoft Office 2003 configurations to the 2007 Office release.

Office Deployment Guide

http://www.microsoft.com/technet/desktopdeployment/bdd/2007/OfficeDep.mspx

If your environment uses public folders, and if you use public folder security forms in earlier versions of Outlook, you can continue to use public folder security forms. You can do this after you make a minor change to the appropriate registry settings. Also, Outlook 2007 is designed to take advantage of the GPO settings to manage security for attachments and for add-ins.

More detailed information can be found in the following article.

Information for administrators about e-mail security settings in Outlook 2007

http://support.microsoft.com/?id=926512

For your convenience, we have listed the previous article of “public folder security forms” of Outlook 2003 below.

How to use Outlook E-mail Security Administrative Package to Trust Add-in or Other Programs

http://blogs.technet.com/asiasupp/archive/2006/11/16/how-to-use-outlook-e-mail-security-administrative-package-to-trust-add-in-or-other-programs.aspx

Thank you.

Microsoft Exchange team is wrapping up the Beta version of Exchange Server 2007 SP1 and it is scheduled to be released sometime after April through TechNet. We are targeting final release for the 2nd half of this year. Our work in this Service Pack is purely in response to our customers’ feedback on earlier releases of Exchange Server 2007.

Check the article at Microsoft Exchange Team Blog website for a quick overview on some of the new features and improvements to be included in SP1

http://msexchangeteam.com/archive/2007/02/23/435699.aspx

More information will be posted in the coming months. Stay tuned.

SMS Advanced Client push installation consists of three main phases. These are:

• Pre-installation phase - The SMS Client Configuration Manager connects to the target client and verifies the client's operating system and client information. The client installation source files are copied, and then the Setup process downloads the SMS core components to the client computer.
•  Installation phase - The SMS Advanced Client copies the installation files from the site server and then starts Setup.
• Post-installation phase - After the Setup program is complete, the SMS Advanced Client obtains a site assignment, sends the heartbeat discovery information to the SMS site server, and then contacts the default management point to retrieve the SMS Advanced Client policy.

There is now a KB article

925282 How to troubleshoot Advanced Client Push Installation issues in Systems Management Server 2003
http://support.microsoft.com/default.aspx?scid=kb;EN-US;925282

The article discusses all three phases, including:

• A brief description of the flow of events for each phase
• Common issues that can occur in each phase and how to troubleshoot and fix them
• Common troubleshooting procedures, such as Using a CCR file to manually trigger client installation
• Management point troubleshooting advice
• Useful log files