Clean it with Atiman Uninstaller v.6.0.0.msi. Download LINK

Run it with administrator privilege. Some antivirus software will give false alarm but it is just a false positive.

Then install Catalyst 11.9 + ( Catalyst 11.8 CAP5 http://www.overclock.net/ati-drivers…11-8-cap5.html only if you are crossfire).

Disable ULPS http://www.overclock.net/amd-ati/667…ling-ulps.html

During Catalyst install, if you get any error messages, ignore it and let it complete. Restart PC, then go to folder where the files extracted/unzipped to, find in CCC2 **.exe then perform repair.

 

After rebooting and finallay loading the drivers, Battlefield 3 worked perfectly!

Thanks!

Here is the batch I used

if %PROCESSOR_ARCHITECTURE%==x86 (

copy \\SERVERNAME\deployment\AppDeploy\Tools\rsclient\x86\*.* /y %windir%\system32\
regsvr32 /s %windir%\system32\rsclientprint.dll

) else (

copy \\SERVERNAME\deployment\AppDeploy\Tools\rsclient\x64\*.* /y %windir%\system32\
regsvr32 /s %windir%\system32\rsclientprint.dll

)

You need to extract the rsclient cab from the reporting server (see image) to a network share, then you need to use admin rights to install (either psexec, sccm or some startup script)

These are the steps to get it to power on at least (not complete)

1. Disassemble phone
2. clean all parts with some electronics cleaner (I actually used alcohol)
3. let dry
4. reassemble
5. I could get it to detect in ADB but then when I attempted to reboot it, it got stuck in download mode and then the power button broke.
6. to get past the no power button, press both volumes and insert barrery (download mode)
7. still trying more now…

I had an issue with xbmc not actually booting into xbmc. It was just booting into the logon prompt (shell)

running

aptitude reinstall xbmc-live

 

Seems to have fixed it..

Remove-Message -filter {MessageSourceName -eq “journaling”} -WithNDR $false

easy

-WithNDR $false

the issue was related to the address book service not running.. It took my ages to find this out also!

I knew it was related to OAB by the way it was failing..

So I ended up spending much more seeing much less. SO MAKE SURE YOU GET IT BEFORE YOU LEAVE!!!!!!!!!

www.japanrailpass.net/eng/en003.html

Here is what I have (you can confirm)

All 2008 R2 X64 fully patched (IPv6 Disabled)

MBX Server
TCP    0.0.0.0:6001           0.0.0.0:0              LISTENING
TCP    [::]:6001              [::]:0                 LISTENING

CAS Server
TCP    0.0.0.0:6001           0.0.0.0:0              LISTENING
TCP    0.0.0.0:6002           0.0.0.0:0              LISTENING
TCP    0.0.0.0:6004           0.0.0.0:0              LISTENING
TCP    0.0.0.0:6005           0.0.0.0:0              LISTENING
TCP    0.0.0.0:6006           0.0.0.0:0              LISTENING
TCP    0.0.0.0:6007           0.0.0.0:0              LISTENING
TCP    0.0.0.0:6008           0.0.0.0:0              LISTENING

TCP    [::]:6001              [::]:0                 LISTENING
TCP    [::]:6002              [::]:0                 LISTENING
TCP    [::]:6004              [::]:0                 LISTENING
TCP    [::]:6005              [::]:0                 LISTENING
TCP    [::]:6006              [::]:0                 LISTENING
TCP    [::]:6007              [::]:0                 LISTENING
TCP    [::]:6008              [::]:0                 LISTENING

Active Directory Domain Controller

TCP    0.0.0.0:6004           0.0.0.0:0              LISTENING
TCP    [::]:6004              [::]:0                 LISTENING

see this : http://code.google.com/p/android/issues/detail?id=11177#c56 ( I only did part 2)

1) Remove the Android mobile devces affected from each users mailboxes.

2) Remove the Default (and any other ActiveSync) policy using EMC  -- Remove-ActiveSyncMailboxPolicy -id <Default>

         Note: this will set all user to no activesync policy (this is what we want temporarily)....

3) Setup the Andriod phones to sync and let them get past the initial syncronization.

4) Recreated the ActiveSync Policy and set it back to default - (this will reapply the policy to all mailboxes).

You need to read this: http://support.microsoft.com/kb/2101557 but essentially its a process of:

• logging in as local\Administrator
• Customising Windows (start menu, desktop etc)
• Creating an “unattended.xml” using WAIK (for windows 7) and placing in the sysprep folder
• Running the “Capture Media”
• Deploying Windows 7 using the xml created before.

I rough guide here.

1. Install Windows 7
2. Choose any default username & login
3. Goto Computer Management & User Accounts
4. Enable the local\administator account
5. Delete the user accounts except local\Administator
6. Reboot
7. Apply all the customisations
8. Save the Unattended.xml to %windir%\system32\sysprep\unattended.xml
9. Insert SCCM Capture media & capture
10. When deploying, Make sure you apply the XML as part of the TS
    

Links:

http://www.windows-noob.com/forums/index.php?/topic/2224-how-to-copy-default-profile-during-sccm-sysprep/

http://support.microsoft.com/kb/2101557http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/8869ebaa-15ec-4e6d-a0f2-e476d1ae66dc#cd98f098-b397-4be6-9637-f0e848d3693a

http://www.leinss.com/vistadeploy.html