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.

 

When you try to uninstall Exchange 2007 from your server, you may receive some error messages which indicate that there is still some Public Folder on the machine thus meaning the uninstall process fails. We have received a lot of these issues recently. It is caused by the Exchange 2007 server containing some public folder replicas. We should remove the replicas as well as the public folder store before we can uninstall Exchange 2007 properly.

For the detailed steps to remove public folder replicas and the public folder store, please refer to the following article.

How to remove Exchange 2007 from a computer

http://support.microsoft.com/default.aspx?scid=kb;EN-US;927464

 

Recently some customers reported an compatiblity issue between IE9 and Forefront TMG2010.

After install IE9, Microsoft Forefront Thread Management Gateway management tools cannot work anymore, it gives error message like “member not found”, “refresh failed”.

And going back to IE8 the problem was resolved. This seems localized IE9 is installed. Gernam and Russian language were reported being affected.

We are investigating this issue, the current workaround is:

Symptom:

You have Windows Server 2003 with installed Certification Authority and Web Enrollment components.

When you try to access web enrollment pages from a Windows Vista-based (or newer) computer you receive error:

The certificate enrollment page you are attempting to access cannot be used with this version of Windows. To enable Web certificate enrollment for clients running Windows Vista, your administrator must update all Windows CA Web enrollment pages. To learn more about this issue and the steps needed to update Web enrollment pages to support all versions of Windows, see:

http://support.microsoft.com/kb/922706

You installed MS11-051 by following KB922706 but you are still getting the same erro.

Solution:

1.  Uninstall Security Update MS11-051.
2.  Install hot fix KB922706
3.  Install Security Update MS11-051.
4.  Type:  IISReset

More information:

Install KB922706 update. Use the links below to download appropriate update:
Download link for Windows Server 2003 x86
Download link for Windows Server 2003 x64

Install MS11-051 security patch. Use the links below to download appropriate update:
Download link for Windows Server 2003 x86
Download link for Windows Server 2003 x64

There is a more conprehensive article authored by Vadims Podans also talking about this issue, please see:

http://en-us.sysadmins.lv/Lists/Posts/Post.aspx?ID=53

 

 

Symptom:

When you backup a VHD to a network share which is a local drive, it may fails with the following error:

The backup operation to \\server\b$\daily\a\ is starting.
Creating a shadow copy of the volumes specified for backup...
Creating a shadow copy of the volumes specified for backup...
The backup of volume System(C:) could not be completed.  Error: The requested operation could not be completed due to a file system limitation
The backup operation stopped before completing.

In the event log, I get the following:

VDS Basic Provider: Unexpected failure.  Error code: 490@01010004

and

Backup: The backup operation that started at '?2010?-?05?-?17T20:54:42.085886000Z' has failed with following error code '2155348041' (None of the source volumes were backed up.).  Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

Root cause:

It's not possible to specify as a Destination Folder a share that is located on the machine (Like \\LocalHost\ShareName) where you are running the backup (in this case, it's the WSB Backup). When you try this, the backup will fail just after finishing the
enumeration of the files (after the snapshot creation and the Writer Initialization) and just before starting the I/O backup operation (i.e: Copying from source to destination). The reason is because we DO NOT SUPPORT opening VHDs from a LOOPBACK SMB CONNECTION.

During a normal Backup Operation, we create on the Target a VHD and we mount it. This VHD will be filled by the content of the source. When we target the backup to a VHD on the network, if the share is on a local drive, we try to make a loopback SMB. By design, this is not supported, and will not work.

Solution:

You need to use either LOCAL Drive or Remote SHARED FOLDER on OTHER Server on your Network.

For by pass this kind of limitation, you can use a complete backup software for Enterprise like System Center Data Protection 2010.

Sometimes you may have a need to load a DLL in a separate domain to call its method at run-time. You can create a proxy class by referencing the following code snippet:

public class Loader : MarshalByRefObject
 {
     object CallInternal(string dll, string typename, string method, object[] parameters)
     {
         Assembly a = Assembly.LoadFile(dll);
         object o = a.CreateInstance(typename);
         Type t = o.GetType();
         MethodInfo m = t.GetMethod(method);
         return m.Invoke(o, parameters);
     }
     public static object Call(string dll, string typename, string method, params object[] parameters)
     {
         AppDomain dom = AppDomain.CreateDomain("MyNewDomain");
         Loader ld = (Loader)dom.CreateInstanceAndUnwrap(Assembly.GetExecutingAssembly().FullName, typeof(Loader).FullName);
         object result = ld.CallInternal(dll, typename, method, parameters);
         AppDomain.Unload(dom);
         return result;
     }
 }

Here are several issues with Remote Server Administration Tools and Windows 7 SP1.

(1) You can not install RSAT on Windows 7 SP1 (http://support.microsoft.com/kb/2517239/en-us).

After installing windows7 service pack 1, remote server administration update tool cannot install on the machine.

The error massage is “this update is not applicable to your computer”.

here is the repro steps if you are interested to test
1.    On a Windows 7 machine, install SP1.
2.    Try to install Remote Server Administration Tools (RSAT).
3.    The error message “this update is not applicable to your computer” will appear.


Workaround:

Uninstall SP1, install RSAT and then apply SP1 again.

Reference:

RSAT tools (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d&displaylang=en)

http://social.technet.microsoft.com/Forums/en/w7itproappcompat/thread/ef1b47e4-85f0-4124-b065-f80461c9e250

http://social.technet.microsoft.com/Forums/en/w7itproSP/thread/0d763f12-30f8-4d13-8534-315d5c34dd0d

http://social.technet.microsoft.com/Forums/en-US/w7itproSP/thread/12d1e8a5-7e43-4ba6-82aa-20b6884128e5

http://social.technet.microsoft.com/Forums/bg-BG/w7itproSP/thread/9d448ef8-ff9a-4917-8476-fd81073b88f7

(2) 0x800f081f when you install Win7 SP1.

When you attempt to install the standalone package for Service Pack 1 for Windows 7/2008 R2, you might get the following error:

0x800f081f  <--This maps to CBS_E_SOURCE_MISSING

You'll be prompted to run the CheckSUR utility and running that utility will not resolve the issue. 

This may be due to a pre-release version of the RSAT tools being installed on the system.  To alleviate this failure, do the following:

1.  Uninstall the pre-release RSAT tools

2.  Reboot the system

3.  Install the release version of the RSAT tools (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d&displaylang=en)

4.  Reinstall SP1.

 Edit:

The Remote Server Administration Toolkit update to support Windows 7 Service Pack 1 has released. Come and get it:

www.microsoft.com/.../details.aspx

Symptom:

You upgraded from Windows 7 Pro to Windows 8 Consumer Preview, but found the Metro apps won't start when clicked. Sometimes, the app appears to start, the screen fills up with a green background with the app logo centered, but nothing happens afterwards.

You might find the following events when starting Metro Apps:

EventId 10010

Description "The server Microsoft.WindowsLive.Calendar.wwa did not register with DCOM within the required timeout."

 

Resolution:

A few things worth trying:

1. Update video card driver and firmware (verify it by switching to the Microsoft Basic Video Driver.)

2. Fix the OLE registry key. Please make sure to backup the registry before changes are made. (http://support.microsoft.com/kb/322756)

Save the below to a .reg file and merge.

====================================

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole]
"MachineLaunchRestriction"=hex:01,00,04,80,90,00,00,00,a0,00,00,00,00,00,00,00,\
  14,00,00,00,02,00,7c,00,05,00,00,00,00,00,18,00,1f,00,00,00,01,02,00,00,00,\
  00,00,05,20,00,00,00,20,02,00,00,00,00,14,00,0b,00,00,00,01,01,00,00,00,00,\
  00,01,00,00,00,00,00,00,18,00,1f,00,00,00,01,02,00,00,00,00,00,05,20,00,00,\
  00,32,02,00,00,00,00,18,00,1f,00,00,00,01,02,00,00,00,00,00,05,20,00,00,00,\
  2f,02,00,00,00,00,18,00,0b,00,00,00,01,02,00,00,00,00,00,0f,02,00,00,00,01,\
  00,00,00,01,02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,01,02,00,00,00,00,\
  00,05,20,00,00,00,20,02,00,00
"MachineAccessRestriction"=hex:01,00,04,80,8c,00,00,00,9c,00,00,00,00,00,00,00,\
  14,00,00,00,02,00,78,00,05,00,00,00,00,00,14,00,07,00,00,00,01,01,00,00,00,\
  00,00,01,00,00,00,00,00,00,14,00,03,00,00,00,01,01,00,00,00,00,00,05,07,00,\
  00,00,00,00,18,00,07,00,00,00,01,02,00,00,00,00,00,05,20,00,00,00,32,02,00,\
  00,00,00,18,00,07,00,00,00,01,02,00,00,00,00,00,05,20,00,00,00,2f,02,00,00,\
  00,00,18,00,03,00,00,00,01,02,00,00,00,00,00,0f,02,00,00,00,01,00,00,00,01,\
  02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,01,02,00,00,00,00,00,05,20,00,\
  00,00,20,02,00,00

 

Alternately you can also delete the OLE key and reboot.

Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole

3. You need at least 1024X768 resolution for Metro apps to work.

4. Metro appsaren’t supported if you are running with a built-in administrator account (happens mostly when upgrading).

5. Check if UAC(User Account Control) is enabled.

Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole

 

Under some circumstances, a domain controller cannot be gracefully demoted due to the required dependency or operation failing. These include network connectivity, name resolution, authentication, Active Directory service replication, or the location of a critical object in Active Directory. As a last resort, we can perform a forced removal of a domain controller from Active Directory to avoid having to reinstall the operating system on a domain controller that has failed and cannot be recovered. When a domain controller can no longer function in a domain (that is, it is offline), you cannot remove Active Directory in the normal way, which requires connectivity to the domain. Forced removal is not intended to replace the normal Active Directory removal procedure in any way. It is virtually equivalent to permanently disconnecting the domain controller.  

---

Here let's go through the procedure to forcefully demote a domain controller (using Windows 2003 SP1 as an example).

Scenario 1: If the domain controller can boot into normal mode:

1. Click Start, click Run, and then type the following command:

        dcpromo /forceremoval

2. Click OK. If Certificate Services is not removed, you will get a message to remove it first. If FSMO roles/GC are not seized from the DC, you will get a message to transfer the roles to another DC.

3. At the Welcome to the Active Directory Installation Wizard page, click Next.

4. At the Force the Removal of Active Directory page, click Next.

5. In Administrator Password, type the password and confirmed password that you want to assign to the Administrator account of the local SAM database, and then click Next.

6. In Summary, click Next.

7. When it finishes, click Finish and reboot the computer.

---

Scenario 2: If the domain controller cannot start in normal mode:

1. Restart the computer, and then press F8 to display the Windows Advanced Options menu. 

2. Choose Directory Services Restore Mode, press ENTER, and then press ENTER again to continue restarting. 

3. Modify the ProductType entry in the registry. To do this, follow these steps:

    a. Click Start, click Run, type regedit , and then click OK. 

    b. Locate the following registry subkey:

         HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ProductOptions 

    c. In the right-pane, double-click ProductType. 

    d. Type ServerNT in the Value data box, and then click OK.

Note If this value is not set correctly or is misspelled, you may receive the following error message:

    System Process - License Violation: The system has detected tampering with your registered product type. This is a violation of your software license. Tampering with product type is not permitted.

    e. Quit Registry Editor. 

4. Restart the computer.

5. Log on with the administrator account and password that is used for Directory
Service Repair mode.

The computer will behave as a member server. However, there are still some
remaining files and registry entries on the computer that are associated with the
domain controller. If the domain controller cannot start in normal mode do the
following:

    - disjoin domained (joined new workgroup)

    - install DNS Server and point to itself

6. Start Registry Editor and locate the following registry entry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
NTDS\Parameters

    If there is an entry for Src Root Domain Srv , right-click the value and then
click Delete. This value must be deleted so that the domain controller sees itself
as the only domain controller in the domain after promotion. Go through the
following keys to delete reference to the old domain controller:

    HKEY_LOCAL_MACHINE\Software\Microsoft\ADS\LDAP\CN=....

    HKEY_LOCAL_MACHINE\System\CCS\DNS
\Parameters|PreviousLocalHostName

    HKEY_LOCAL_MACHINE\System\TCP
\Services\TCPIP\Parameters|Domain and NV Domain 

7. Remove the remaining files and registry entries. To do this, follow these steps:

    a. Start the Active Directory Installation Wizard. 

    b. Install Active Directory to make the computer a domain controller for a new, temporary domain, such as "psstemp.deleteme."

Note Make sure that you make the computer a domain controller in a different forest. 

    c. After you install Active Directory, start the Active Directory Installation Wizard again, and then remove Active Directory from the domain controller.

Perform a metadata cleanup for the demoted domain controller on a surviving domain controller in the forest. Active Directory stores a considerable amount of metadata about a domain controller. During the normal process of uninstalling Active Directory on a domain controller, this metadata is removed from Active Directory through a connection to another domain controller in the domain. A forced removal assumes that there is no connectivity to the domain; therefore, it does not attempt any metadata removal (cleanup).

Consequently, forced removal of Active Directory from a domain controller should always be followed by the metadata cleanup procedure, which removes all references to the domain controller from the domain and forest. For more details, view the following KB article:

    How to remove data in Active Directory after an unsuccessful domain controller demotion

 

-End-  

Author: Pearson Peng

Symptom:

When you are installing Windows 7 or Windows Server 2008 R2 SP1, you may encounter the installatin failure with error 0x80004005 (E-FAIL).

And you can find the errors in the CBS.log, like below:

Failed. Attempted to uninstall a version of a non-driver component that is not installed, version: 0X600011db04001, component: x86_microsoft-windows-a..tigations.resources_31bf3856ad364e35_6.1.7600.16385_en-us_1992d6abf12a4412, owner: Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Windows Foundation Language Pack [HRESULT = 0x80004005 - E_FAIL]

Or

2011-02-21 18:56:58, Error CSI 000006e1 (F) Done with generic command 60 (0x0000003c); CreateProcess returned 0, CPAW returned S_OK
Process exit code 41001 (0x0000a029) resulted in success? FALSE
Process output: [l:73 [73]"Trying to install vpcnfltr .....failed. Error code: 0x8004a029. [gle=0x80004005]

Error code: 0x8004a029 is NETCFG_E_MAX_FILTER_LIMIT

Resolution:

Generally, the error is because of system corruptions.

Please follow the below steps to resolve it:

1. Run CheckSUR(KB947821).

http://support.microsoft.com/kb/947821

2. Run sfc/scannow to fix the possible errors.

3. If you find 0x8004a029 in the CBS.log, it is because you have more than 13 filter drivers installed.

Option 1
Windows 7 is hard coded to allow 14 filter drivers, but the following registry sets the limit to 8 by default. You can adjust the amount up to 14 or delete this key and it will be set to max of 14.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\MaxNumFilters

Option 2
Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4d36e974-e325-11ce-bfc1-08002be10318}\

Delete Something that you don't need (Export First) - You can delete for example Virtual WiFi Filter Driver

4. If you encounter this error on a MacBook, probably it is an known issue (http://discussions.info.apple.com/thread.jspa?threadID=2762246&start=0&tstart=0).

Just uninstalled the HFS+ driver, then SP1 ran from Windows Update and it installed fine.

5. The last option is to Perform an inplace upgrade of Windows

Reference:

=========

http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/2b4a26e0-ee31-4bfa-a8bc-82b0af24af1d

http://social.technet.microsoft.com/Forums/el-GR/w7itproinstall/thread/3cd82850-717d-45af-bd67-54823a9b5846

http://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/2538adfa-0872-4400-8a20-12abdde248df

http://social.technet.microsoft.com/Forums/en-MY/w7itproSP/thread/b3efd2f5-3b00-41c1-89ce-f48618e29e4c

http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/3a2e8c69-ec05-43d9-9ae4-836630b55f82

http://answers.microsoft.com/en-us/windows/forum/windows_other-windows_update/sp1-wont-install-error-code-80004005/3c78e4fc-68ce-467d-851e-8f30f0e93bfd

http://social.technet.microsoft.com/Forums/en-US/w7itproSP/thread/971838ad-39c0-4e16-9ea2-1dcb8a885ca1

 

Edit: KB2530477 was published, you can reference it for more details.

Sometimes you may encounter the script error when you attempte to load album/track information in WMP12. For example:

An error has occurred in the script on this page

Line: 240

Character: 25

Error: Object expected

Code: 0

URL: http://fai.music.metaservices.microsoft.com/FAI/AlbumMatch.aspx?locale=409&geoid=f4&version=12.0.7601.17514&userlocale=409&requestid=830A4FFD-F3A3-4AD9-A1FA-390A48236E10

Do you want to continue running scripts on this page? Yes or
No.

 

Causes:

In most of cases, it is due to Internet Explorer can not load the pages. You can fix it by cleaning the IE temp. files.

 

Resolution:

1. Close the WMP.

2. Please follow http://support.microsoft.com/kb/260897 to delete internet temp. files. Fix-it is recommended.

Symptom:

Customers installed Win8 and got the following error:

“We are not sure what happened, but couldn't finish installing windows 8 Consumer Preview. We've set your PC back to the way it was right before you started.”

 

Resolution:

Running setup from the root of the media within an existing Windows installation assumes that you want to perform a clean installation with data migration.

Running setup from the sources folder gives more of a Windows 7-like experience where it asks you what you want to do.

Symptom:

You installed the Win8 Server Beta without issue, but you are unable to install any roles or features like Hyper-V role. It just fails, no events in the Event Log.

You can install Hyper-V role through powershell (e.g. Dism /online /enable-feature /featurename:Microsoft-Hyper-V), but you can not start any VM you created.

 

Resolution:

This is a known issue with the beta.  Specifically - the user locale and the system locale need to match (they should not need to be English - just the same).

You can also change it in the Control Panel and Region. (Some customers reported the Format must be English (United States)).

Symptom:

Customer has installed a Hyper-V Cluster. The host os is Windows Server 2008 R2 with SP1. When he runs cluster validation wizard, the wizard shows lots of missing updates, however those updates are already in SP1 package. When he checks for updates from Windows Update, no new updates are detected.

He is unable to install the "missing update" saying they are already on the system. This is usually seen after Add Node.

This problem does not happen when hosts are installed with stock Windows Server 2008 R2 and applied SP1 later.

 

Root Cause:

Validate compares the hotfix numbers, not the binary versions. Because hotfixes and SP's are cumulative, there can be cases where you install a cumulative hotfix and Validate gives a false positive.

Repro steps:

1. Node1 = Hotfix 1, then SP1

2. Node2 = Hotfix 1, then SP1

3. Add Node3 = SP1, now Node1 = Node2 = Node3

4. Validate reports Hotfix1 is missing on Node3

 

Resolution:

On Node3, uninstall SP, install hotfixes then apply SP again. Actually you can ignore this Validate warning!

Symptom:

After SharePoint 2010 SP1 and June CU
upgrade, when customer goes into Central Admin->manage user profile service
app->manage user profiles, select a user, he cannot uploaded their profile
picture any more, when he click choose picture and upload, it threw this error
"There was an error saving the picture. Please try again later.", he
does not see anything in the ULS log. The user is able to upload their own
pictures however not the admin.

 

Root cause:

This seems to be a known issue of June CU. The fix is under development and will be released soon.

 

Current workaround:

Use powershell script to do the update.

You can reference the sampe script in the link http://get-spscripts.com/2010/12/upload-multiple-user-profile.html as a temp. workaround.

This is an interesting issue of Windows 7.

Some customers reported that in the Power Options they have chosen 'Never' for 'Turn off the display'. However it keeps resetting itself to 20 minutes.

After further investigation, it was proved to be a compatibilty issue of HD Tunes Pro. That software is for hard drives testing and each time any test starts it resets power options.

Symptom:

You've implemented federation (AD FS) in your on-premises organization. You are doing a staged Exchange Migration (using a CSV file). You have migrated a couple of mail boxes from on-premises Exchange server to Plan E3. 

But you start getting error:

A Windows Live error occurred while provisioning for "mail@domain.com". An internal error occurred while talking to Windows Live. Additional details: "0x800482101033This action is currently blocked for the API.
CH1IDOPRTI02 2011.07.22.15.10.19".

Resolution:

Please check in the CSV file, are youusing TRUE for the value of the ForceChangePassword attribute?

If so, then in the CSV file, change the value for ForceChangePassword to FALSE, and then rerun the migration.  For example:

EmailAddress,Password,ForceChangePassword
pilarp@tailspintoys.com,Pa$$w0rd,False
tobyn@tailspintoys.com,Pa$$w0rd,False
iant@tailspintoys.com,Pa$$w0rd,False

Alternatively, you can remove the Password and ForceChangePassword columns. The documentation for staged Exchange migration will be updated accordingly.

A lot of customers complained the following:
When they open up the Task Scheduler, they get a message that says:
The selected task "{0}" no longer exists. To see the current tasks, click Refresh.

 The mechamism task scheduler uses: it has a copy of tasks in registry and a copy of them in task files on disk. If somehow the tasked stored in registry and on disk are not in sync, users will encounter such issues as reported.

Tasks are stored in C:\Windows\System32\Tasks

In Registry, related branches are located in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks

Tasks tree is stored in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft

So the general troubleshooting steps are starting from checking these locations to see if anything is broken or inconsistent.

Reference:

 http://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/69afe198-3f97-406a-8d91-6a17504fb5b5

http://social.technet.microsoft.com/Forums/en-IE/w7itproinstall/thread/273368d4-ed12-4107-9d52-34759f2b53aa

http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/1f677dd3-bdb7-4650-9164-d8e2c66b7708

http://social.technet.microsoft.com/Forums/en/w7itprogeneral/thread/d584f7e4-4e4c-45e8-8bce-39414914d674

http://social.technet.microsoft.com/Forums/en/w7itprogeneral/thread/a9e485d3-06ba-4038-a9b8-1b58e73ea4dd

http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/360fde7c-ec4e-41f2-ae74-8949218e7a06

http://social.technet.microsoft.com/Forums/en/w7itprosecurity/thread/8e779ed1-7200-482e-a3a4-1e0ba8bf17cc

http://social.technet.microsoft.com/Forums/en/w7itproperf/thread/94bb210a-b291-41ad-a745-d4a9d8cc77dc

http://social.technet.microsoft.com/Forums/en/w7itprogeneral/thread/344f6815-0878-43ab-8997-33790b889541

http://social.technet.microsoft.com/Forums/pl-PL/w7itproperf/thread/43712af2-5731-4177-9d45-31d9b5b3240d

 

 

 

 

There are many possible causes that can crash MSQuery in office 2010. A typical crash is as below:

AppName: msqry32.exe AppVer: 14.0.4750.1000 ModName: msvcr90.dll

There are several possible resolution you can try to resolve the above crash:

1. When you launch MS Query, just disable the option "Validate queries before saving or returning data", this is the fifth box in the options menu.

The only problem is that if you have made any mistake in your query, you'll only be noticed when receiving the data in excel.

 

2. Repair all the keys into registry at the following place:

[HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\ODBC]

For example:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\ODBC]
"TraceFile"="C:\\DOCUME~1\\...USERNAME...\\IMPOST~1\\Temp\\SQL.LOG"
"TraceDll"="C:\\WINDOWS\\system32\\odbctrac.dll"

In some cases ODBC trace/analyze log is off and can't create a big SQL.LOG file size that cause msvcr90.dll crash

 

Assuming you need it in script, PowerShell:

 

(gwmiWin32_LogonSession).GetRelated("Win32_UserAccount")

 

If you expect more than one logon session, then

 

(gwmi Win32_Process -filter "Handle = $Pid").GetRelated("Win32_LogonSession") |% {$_.GetRelated("Win32_UserAccount")}

 

will give you Win32_UserAccount for the account used to run current powershell instance.

Assuming you need it in script, PowerShell:

# computername

$MachineName = 'localhost'

 

# open HKLM reg on $MachineName

$reg = [Microsoft.Win32.RegistryKey]::OpenRemoteBaseKey('LocalMachine', $MachineName)

 

# open subKey SYSTEM\CurrentControlSet\services\TCPIP6\Linkage

$regKey = $reg.OpenSubKey("SYSTEM\\CurrentControlSet\\services\\TCPIP6\\Linkage")

 

# get the values from the name 'Bind'

# e.g. \Device\{A2B312D5-A133-4779-B21B-5B3ED82B6DCF}

$bind = $regKey.GetValue("bind")

 

# get adapters that are IP enabled : e.g. IPv4 or IPv6 is active

$adapters = gwmi -computer $MachineName Win32_NetworkAdapterConfiguration|?{$_.IPEnabled}

 

# for each adapter check if his GUID is in the Bind values and display info regarding IPv6 binding

foreach ( $adap in $adapters)

   
{

       
# get GUID of the adapter

           
$guid = $adap.SettingID

           
# get the name of the adapter to be used to display info

       
$name = (gwmi -computer $MachineName Win32_NetworkAdapter|?{$_.guid -eq $guid}).NetConnectionID

           
# buid the \device\GUID string from the GUID of the adapter

       
$device_guid = '\Device\'+$guid

           
# check if the bind key contains the adapter guid

       
if($bind -contains $device_guid)

            
{write-host "Computer $MachineName -> IPv6 OK in adapter: $name" }

       
else {write-host "Computer $MachineName -> IPv6 not bind on adapter: $name" }

   
}

Write `nDone  

You can use the below script:

==================================

Get-SPDatabase $syncdb=Get-SPDatabase -Id

$syncdb.Unprovision()
$syncdb.Status='Offline'
Get-SPServiceApplication
$upa=Get-SPServiceApplication - Id
$upa.ResetSynchronizationMachine()
$upa.ResetSynchronizationDatabase()
$syncdb.Provision()

 

This is the sample code in CPP to show how to wait on a job object. In the documentation:

 

The state of a job object is set to signaled when all of its processes are terminated because the specified end-of-job time limit has been exceeded. Use WaitForSingleObject or WaitForSingleObjectEx to monitor the job object for this event.

 

If the processes terminate normally, then the job object is not signaled. To detect when all processes in a job have terminated, you need to associate the job with a completion port, and then listen on the I/O completion port for the JOB_OBJECT_MSG_ACTIVE_PROCESS_ZERO notification.

=================================

#define UNICODE

#define _UNICODE

#define STRICT

#include
<windows.h>

#include
<stdio.h>

#include
<atlbase.h>

#include <atlalloc.h>

#include
<shlwapi.h>

 

int __cdecl wmain(int argc, PWSTR argv[])

{

   
CHandle Job(CreateJobObject(nullptr, nullptr));

    if(!Job) {

       
wprintf(L"Could not create job object, error %d\n", GetLastError());

       
return 0;

    }

 

   
CHandle IOPort(CreateIoCompletionPort(INVALID_HANDLE_VALUE, nullptr, 0, 1));

    if(!IOPort) {

       
wprintf(L"Could not create IO completion port, error %d\n",GetLastError());

       
return 0;

    }

 

   
JOBOBJECT_ASSOCIATE_COMPLETION_PORT Port;

   
Port.CompletionKey = Job;

   
Port.CompletionPort = IOPort;

    if(!SetInformationJobObject(Job, JobObjectAssociateCompletionPortInformation,&Port, sizeof(Port))) {

       
wprintf(L"Could not associate job with IO completion port, error %d\n", GetLastError());

       
return 0;

    }

 

   
PROCESS_INFORMATION ProcessInformation;

   
STARTUPINFO StartupInfo = { sizeof(StartupInfo) };

   
PWSTR CommandLine = PathGetArgs(GetCommandLine());

 

    if(!CreateProcess(nullptr, CommandLine, nullptr, nullptr, FALSE,CREATE_SUSPENDED, nullptr, nullptr, &StartupInfo, &ProcessInformation))
{

       
wprintf(L"Could not run process, error %d\n", GetLastError());

       
return 0;

    }

 

    if(!AssignProcessToJobObject(Job, ProcessInformation.hProcess)) {

       
wprintf(L"Could not assign process to job, error %d\n",
GetLastError());

       
return 0;

    }

 

   
ResumeThread(ProcessInformation.hThread);

   
CloseHandle(ProcessInformation.hThread);

   
CloseHandle(ProcessInformation.hProcess);

 

   
DWORD CompletionCode;

   
ULONG_PTR CompletionKey;

   
LPOVERLAPPED Overlapped;

 

   
while (GetQueuedCompletionStatus(IOPort, &CompletionCode,&CompletionKey, &Overlapped, INFINITE) && CompletionCode !=JOB_OBJECT_MSG_ACTIVE_PROCESS_ZERO) {

       
wprintf(L"Still waiting...\n");

    }

 

   
wprintf(L"All done\n");

 

   
return 0;

}

After we understand how UAC works and realize the importance of enabling UAC to prevent potential problems that may arise during your Windows Vista deployment in
your environment, we can move on to discussing how to configure UAC to optimize 
security and ease of use. The consent UI behavior as well as some other UAC 
features can be changed by group policy for administrators. 

This section details the main method for configuring UAC by Administering 
UAC with the local Security Policy Editor and Group Policy. 
For administrators in a domain environment, they can configure UAC 
settings in domain security policy.

1.    Click Start, click All Programs, click Accessories, click Run, type secpol.msc in the Open text box, and then click OK.

2.    From the Local Security Settings console tree, click Local Policies, and then Security Options.

3.    Scroll down and double-click corresponding UAC policy settings to configure

4.    Close the Local Security Settings window.

 

There are in total eight Group Policy Object (GPO) settings that can be configured for UAC. The following list includes the policy settings:

 

User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode

User Account Control: Behavior of the elevation prompt for standard users

User Account Control: Detect application installations and prompt for elevation

User Account Control: Only elevate executables that are signed and validated

User Account Control: Run all administrators in Admin Approval Mode

User Account Control: Switch to the secure desktop when prompting for elevation

User Account Control: Virtualize file and registry write failures to per-user locations

User Account Control: Admin Approval Mode for the Built-in Administrator account

User Account Control: Only elevate UIAccess applications that are installed in secure locations

Hereby we outline three common tasks that administrators perform during the set up and configuration of client computers running Windows Vista. The following policies brief the tasks of disabling Admin Approval Mode, disabling UAC from prompting for credentials to install applications, and changing the elevation prompt behavior.

 1. Disable Admin Approval Mode

Policy Item: User Account Control: Run all administrators in Admin Approval Mode.

Default Value: Enabled
Description: There are two possible values:

• Enabled - Both administrators and standard users will be prompted when attempting to perform administrative operations. The prompt style is dependent on policy.

• Disabled - UAC is essentially "turned off" and the AIS service is disabled from automatically starting. The Windows Security Center will also notify the logged on user that the overall security of the operating system has been reduced and will give the user the ability to self- enable UAC.

Note: Changing this setting will require a system reboot.

 2. Disable User Account Control from prompting for credentials to install applications

Policy Item: User Account Control: Detect application installations and prompt for elevation.

Default Value: Home: Enabled. Enterprise: Disabled
Description: There are two possible values:

• Enabled - The user is prompted for consent or credentials when Windows Vista detects an installer.

• Disabled - Application installations will silently fail or fail in a non-deterministic manner. Enterprises running standard users desktops that leverage delegated installation technologies like GPSI or SMS will disable this feature. In this case, installer detection is unnecessary and therefore not required.

 3. Change the elevation prompt behavior

 Policy Item: User Account Control: Behavior of the elevation prompt for administrators.

Default Value: Prompt for consent
Description: There are three possible values:

• No prompt – The elevation occurs automatically and silently. This option allows an administrator in Admin Approval Mode to perform an operation that requires elevation without consent or credentials. Note: this scenario should only be used in the most constrained environments and is NOT recommended.

• Prompt for consent – An operation that requires a full administrator access token will prompt the administrator in Admin Approval Mode to select either Continue or Cancel. If the administrator clicks Continue, the operation will continue with their highest available privilege.

• Prompt for credentials – An operation that requires a full administrator access token will prompt an administrator in Admin Approval Mode to enter an administrator user name and password. If the user enters valid credentials, the operation will continue with the applicable privilege.

Policy Item: User Account Control: Behavior of the elevation prompt for standard users

Default Value: Home: Prompt for credentials. Enterprise: No prompt
Description: There are two possible values:

• No prompt – No elevation prompt is presented and the user cannot perform administrative tasks without using Run as administrator or by logging on with an administrator account. Most enterprises running desktops as standard user will configure the “No prompt” policy to reduce help desk calls.

• Prompt for credentials – An operation that requires a full administrator access token will prompt the user to enter an administrative user name and password. If the user enters valid credentials the operation will continue with the applicable privilege.

 

For more information on how to configure UAC via policy, view the following links:

 

How to use User Account Control (UAC) in Windows Vista

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

 

http://technet.microsoft.com/en-us/windowsvista/aa905117.aspx

Symptom:

When you are migrating mail boxes from your Exchange server to Plan E3.

• You've implemented federation (AD FS) in your on-premises organization.
• Your are doing a staged Exchange Migration (using a CSV file).
• In the CSV file, you're using TRUE for the value of the ForceChangePassword attribute.

You might get the following error:

A Windows Live error occurred while provisioning for "mail@domain.com". An internal error occurred while talking to Windows Live. Additional details: "0x800482101033This action is currently blocked for the API.
CH1IDOPRTI02 2011.07.22.15.10.19

 

Resolution:

Modify the CSV file, change the value for ForceChangePassword to FALSE, and then rerun the migration.  For example:

EmailAddress,Password,ForceChangePassword
pilarp@tailspintoys.com,Pa$$w0rd,False
tobyn@tailspintoys.com,Pa$$w0rd,False
iant@tailspintoys.com,Pa$$w0rd,False

Alternatively, you can remove the Password and ForceChangePassword columns. The documentation for staged Exchange migration will be updated accordingly.