Mouse Integration Incompatible w/ SMS 2003 Advanced Client

Ref Setup:
http://wikis.sun.com/display/VDI3/Getting+Started+-VDIDemo
Ref Bugs:
http://www.virtualbox.org/ticket/414
http://www.virtualbox.org/ticket/1324
Ref Docs:
http://support.microsoft.com/kb/933986
http://technet.microsoft.com/en-us/sms/bb676787.aspx
Problem:
In VirtualBox 2.0.8, the Mouse Integration is incompatible with Microsoft SMS 2003 Advanced Client software.
Our security policy requires Windows desktops to be joined to an Active Directory domain along
with installation of the SMS client.
Verification:
The SMS client was removed using the "Advanced Client and Management Point Cleaner" (Ccmclean.exe).
After client removal, the VM was rebooted and the Mouse Integration worked normally.

Ref Docs:
Device Manager does not display devices...
http://support.microsoft.com/kb/315539
Mouse integration with Windows XP
http://forums.virtualbox.org/viewtopic.php?t=3467&highlight=&sid=fe45fab05155cec7c7a0412f02dc5d68
Problem:
After joining the Windows XP SP3 VM to our AD domain, the SMS client was automatically
reinstalled. The incompatibility with Mouse Integration reappeared after reboot.
Workaround:
Disabled the following "Hidden Devices" under Device Manager and rebooted:
- Display adapters
Microsoft SMS Mirror Driver (disabled)
- Mice and other pointing devices
SMS Virtual Mouse (disabled)

Similar Messages

Re-Installing SMS 2003 Advanced Client

I'm looking for some help to sort out the mess someone has made of our SMS 2003 environment.
From what I have managed to piece together a collection has been deleted using "delete special" so all the resources (over 2000 machines) have been taken out. The resources have started to re-appear but they aren't reporting they have a client
installed and about 18 hours ago an attempt was made to push the advanced client out to all machines with include only clients assigned to the site, subcollections and always install ticked but nothing new is showing up in the admin console. Most of the warning
messages in the log report either The platform is not supported by the advanced client (all machines are either XP SP3 of Win 7 SP1) or operating system reported error 5 access is denied.
Our AD system discovery is set to run every 4 hours and heartbeat discovery is set to daily.

I will assume that by now things are all good, but see no update since the initial posting. For reference, it is a Heartbeat DDR that will get clients to report in as a client. So they should have started to report in as clients the next day, assuming that
Heartbeat Discovery was set to daily. AD Discovery has nothing to do with client reporting, as AD does not know that a system is a client (or not), only the client knows, and that comes from Heartbeat.
If you are good, can you mark this thread as answered so that we know all is good?
Wally Mead

Best practice for client migration from SMS 2003 to SCCM 2012 R2?

Can anyone advise what the most recommended method is for migrating SMS 2003 clients (Windows 7) to SCCM 2012 R2?
Options are:
1. SMS package to deploy ccmclean.exe to uninstall SMS 2003 client. Deploy SCCM 2012 R2 client via SCCM console push.
2. Simply push SCCM client from console installing over existing SMS 2003 client.
I am finding some folks saying this is ok to do but others saying no it is not supported by Microsoft. Even if it appears to work I do not want to do it if it is not supported by Microsoft. Can anyone provide a definitive answer?
3. Use a logon script or Group Policy preference to detect the SMS client and delete it using CCMclean and then install the SCCM client.
Appreciate any feedback. Thank you.

Hi,
>>I am finding some folks saying this is ok to do but others saying no it is not supported by Microsoft. Even if it appears to work I do not want to do it if it is not supported by Microsoft. Can anyone provide a definitive answer?
I haven't seen any official document records the option 2 method. There is only upgrading from SCCM 2007 to SCCM 2012 directly.
I think you could use a logon script or Group Policy preference to detect the SMS client and delete it using CCMclean.exe. Then use SCCM 2012 to discover these computers and push clients to them.
Best Regards,
Joyce

Migrating Clients from SMS 2003 to SCCM 2012 R2. Best method?

I have set up a new SCCM 2012 R2 server to replace our existing SMS 2003.
Our client systems (all Windows 7 SP1 x64 and x86) still have the SMS 2003 client installed but I would like to move them over to the SCCM 2012 R2 server now. I know there are several methods for installing the SCCM client (manual, push, group policy) but
none of these provide a way to uninstall the old client.
Is there a best practice or commonly used process for doing this? Should I be getting rid of the SMS client first by logon script or some other method and the pushing the SCCM client or some other way? Thank you for any advice.

More info:
Can I manage SMS 2003 clients with System Center 2012 Configuration Manageror migrate SMS 2003 sites and clients to System Center 2012 Configuration Manager?
http://technet.microsoft.com/library/gg682088.aspx#FAQ_Migration
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Upgrading SMS 2003 client to SCCM 2012 clients

How can we upgrade the existing SMS 2003 client to SCCM 2012 client. We are planning to upgrade our existing sms 2003 environment to SCCM 2012. It will be a fresh installation and side by side. My question is ...
1 can we upgrade the existing client to new version? How?
2 can we have both clients on same system?
Want to know the best possible way....for doing this.
Appreciate your suggestions/help....
Ravi.

Ravi,
There is no upgrade path from 2003 to 2012. You can create a package in 2003 to uninstall and then install the 2012 client. There may be better ways to do this but at the moment that is what I have seen done in the past. The only other
solution I have dealt with was an OS refresh since the 2003 client most likely is running on XP systems?
Kris
I faced this situation, where we have old SMS2003 system with XP clients, and W7 migration is planned on 2012. Uninstallation of old ccmsetup is okay, but then offcourse all activity stops and new client is not installed within the same process. I put
everything on the same bat file, like ccmsetup.exe /uninstall and ccmsetup /mp:primarysiteserver... old client goes away, but then nothing happens.

The SMS Advanced Client has determined that its policy is incorrect

I've found a couple of similar threads on here with this issue, but the circumstances have been somewhat different and I am still trying to find a resolution.
We are running SCCM 2007 R3. On every computer in our environment, the following event log entry appears every day. I'd like to know why it is happening and how to get rid of it.
Log Name:      Application
Source:        SmsClient
Date:          9/19/2011 7:59:07 AM
Event ID:      10805
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      XXXXX
Description:
The SMS Advanced Client has determined that its policy is incorrect. A full policy update will be requested to correct the issue. For more information see PolicyAgent.log on the client machine.

Here is a snippet from my policyevaluator.log - I'm not seeing anything of particular interest here, am I missing something?
Raising event:
instance of CCM_PolicyAgent_PolicyEvaluationComplete
ClientID = "GUID:371B6A81-1FF0-4A63-B6D2-59608A7FE672";
DateTime = "20110919143918.885000+000";
PolicyNamespace = "\\\\IT-PC4871\\ROOT\\ccm\\Policy\\S_1_5_21_36134387_1236994427_903097961_25607\\RequestedConfig";
ProcessID = 2592;
ThreadID = 4808;
PolicyAgent_PolicyEvaluator 9/19/2011 7:39:18 AM 4808 (0x12C8)
Updating settings in
\\it-pc4871\root\ccm\policy\machine\actualconfig PolicyAgent_PolicyEvaluator 9/19/2011 7:40:16 AM 7872 (0x1EC0)
Settings update not required. No changes detected. PolicyAgent_PolicyEvaluator 9/19/2011 7:40:16 AM 7872 (0x1EC0)
Raising event:
instance of CCM_PolicyAgent_SettingsEvaluationComplete
ClientID = "GUID:371B6A81-1FF0-4A63-B6D2-59608A7FE672";
DateTime = "20110919144016.382000+000";
PolicyNamespace = "\\\\it-pc4871\\root\\ccm\\policy\\machine\\actualconfig";
ProcessID = 2592;
ThreadID = 7872;
PolicyAgent_PolicyEvaluator 9/19/2011 7:40:16 AM 7872 (0x1EC0)
Updating settings in
\\it-pc4871\root\ccm\policy\s_1_5_21_36134387_1236994427_903097961_25607\actualconfig PolicyAgent_PolicyEvaluator 9/19/2011 7:41:18 AM 7920 (0x1EF0)
Raising event:
instance of CCM_PolicyAgent_SettingsEvaluationComplete
ClientID = "GUID:371B6A81-1FF0-4A63-B6D2-59608A7FE672";
DateTime = "20110919144119.392000+000";
PolicyNamespace = "\\\\it-pc4871\\root\\ccm\\policy\\s_1_5_21_36134387_1236994427_903097961_25607\\actualconfig";
ProcessID = 2592;
ThreadID = 7920;
PolicyAgent_PolicyEvaluator 9/19/2011 7:41:19 AM 7920 (0x1EF0)
Triggered update of logged-on user settings PolicyAgent_PolicyEvaluator 9/19/2011 7:54:08 AM 3276 (0x0CCC)
Evaluating policy in
\\IT-PC4871\ROOT\ccm\policy\machine\requestedconfig PolicyAgent_PolicyEvaluator 9/19/2011 7:54:12 AM 3936 (0x0F60)
Applying policy CSR20008-CSR00008-E008F92D PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy CSR2000C-CSR00009-DBBBC9D6 PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy CSR20076-CSR0003D-DBBBC9D6 PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy CSR200AC-CSR0004B-7D1B5B9B PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy CSR200C3-CSR00042-EC5A5039 PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy CSR200DB-CSR00070-221FBB8C PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy CSR200F9-CSR0004A-926C17AC PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy CSR2012C-CSR00089-DBBBC9D6 PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy CSR201F8-CSR0004A-1455B7D9 PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy CSR2020B-CSR0004A-849F62FF PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy CSR2020E-CSR0004A-153F1250 PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy DEP-CSR2012C-CSR00088-31A28E80 PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy DEP-CSR2012C-CSR00088-412FC222 PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {034b9d39-26fe-431a-93de-015bb7f79c0a} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {06368e74-da19-4644-8467-6393670d7853} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {0eb00e0e-cd76-40e3-b465-cddb858bd204} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {14D84263-FBCE-4D15-9200-82828A913155} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {1620B7B5-AC6F-416A-A622-DCCEDAFF6BFE} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {22f8cd33-b080-4837-8204-f58ba4ef3360} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {2664cada-b22c-43a8-b5ff-08742a522a22} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {2aa83e60-7040-4153-845a-14716ec587a4} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {3494cceb-7f84-4efe-9907-735d282097e5} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {374eea5b-43fd-425c-b360-3b000f4bf04b} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {72b743d2-9809-4654-b0aa-758799207e28} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {72fa590c-be14-45a0-8a25-dfa405c4ab43} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {7584ae37-23f2-42af-a94e-264bec686d74} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {7f93a927-3a1b-4bb8-80a4-0474be87914f} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {855aace3-ae63-43f3-ac1f-c361b06090a0} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {8730AFC8-2B4D-4FD7-BCD8-BD6D30D57E04} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {8B1E0796-7374-443C-AB04-FD17198E1B8D} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {90d91276-05f9-4909-851e-818bbecba4b3} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {a583a7d3-ade7-4522-851d-771eaa49f6c8} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {a5b80a59-393c-4510-bb22-0543a198e708} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {B281AB1A-77A0-4386-89FA-DC4AEBE15CAF} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {b296c946-7707-4cf4-80c5-06fe08185edf} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {d28a0a2d-f674-4631-bad1-29e553a16ebb} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {dc1a0735-0e8b-4a1c-9928-8fa36ea383f2} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {dd244f8f-b760-44a4-af65-aef92b5e4d33} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {dd55a2b7-203d-4ef7-9d69-c2de863496d7} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {e30516b6-e2b9-47b2-8261-964d7156887b} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {e442e9dd-bc90-41a5-96af-de41f7cbb7eb} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Applying policy {f8448e2b-e247-447b-9888-aad08d862228} PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Raising event:
instance of CCM_PolicyAgent_PolicyEvaluationComplete
ClientID = "GUID:371B6A81-1FF0-4A63-B6D2-59608A7FE672";
DateTime = "20110919145413.189000+000";
PolicyNamespace = "\\\\IT-PC4871\\ROOT\\ccm\\policy\\machine\\requestedconfig";
ProcessID = 2600;
ThreadID = 3936;
PolicyAgent_PolicyEvaluator 9/19/2011 7:54:13 AM 3936 (0x0F60)
Evaluating User policy for 'S-1-5-21-36134387-1236994427-903097961-25607' PolicyAgent_PolicyEvaluator 9/19/2011 7:54:33 AM 2272 (0x08E0)
Evaluating policy in
\\IT-PC4871\ROOT\ccm\Policy\S_1_5_21_36134387_1236994427_903097961_25607\RequestedConfig PolicyAgent_PolicyEvaluator 9/19/2011 7:54:33 AM 2272 (0x08E0)
Raising event:
instance of CCM_PolicyAgent_PolicyEvaluationComplete
ClientID = "GUID:371B6A81-1FF0-4A63-B6D2-59608A7FE672";
DateTime = "20110919145433.651000+000";
PolicyNamespace = "\\\\IT-PC4871\\ROOT\\ccm\\Policy\\S_1_5_21_36134387_1236994427_903097961_25607\\RequestedConfig";
ProcessID = 2600;
ThreadID = 2272;
PolicyAgent_PolicyEvaluator 9/19/2011 7:54:33 AM 2272 (0x08E0)
Triggered update of logged-on user settings PolicyAgent_PolicyEvaluator 9/19/2011 7:54:39 AM 2136 (0x0858)
Updating settings in
\\it-pc4871\root\ccm\policy\s_1_5_21_36134387_1236994427_903097961_25607\actualconfig PolicyAgent_PolicyEvaluator 9/19/2011 7:54:39 AM 2272 (0x08E0)
Raising event:
instance of CCM_PolicyAgent_SettingsEvaluationComplete
ClientID = "GUID:371B6A81-1FF0-4A63-B6D2-59608A7FE672";
DateTime = "20110919145439.518000+000";
PolicyNamespace = "\\\\it-pc4871\\root\\ccm\\policy\\s_1_5_21_36134387_1236994427_903097961_25607\\actualconfig";
ProcessID = 2600;
ThreadID = 2272;
PolicyAgent_PolicyEvaluator 9/19/2011 7:54:39 AM 2272 (0x08E0)
Updating settings in
\\it-pc4871\root\ccm\policy\machine\actualconfig PolicyAgent_PolicyEvaluator 9/19/2011 7:56:16 AM 3172 (0x0C64)
Raising event:
instance of CCM_PolicyAgent_SettingsEvaluationComplete
ClientID = "GUID:371B6A81-1FF0-4A63-B6D2-59608A7FE672";
DateTime = "20110919145617.174000+000";
PolicyNamespace = "\\\\it-pc4871\\root\\ccm\\policy\\machine\\actualconfig";
ProcessID = 2600;
ThreadID = 3172;
PolicyAgent_PolicyEvaluator 9/19/2011 7:56:17 AM 3172 (0x0C64)
Updating settings in
\\it-pc4871\root\ccm\policy\s_1_5_21_36134387_1236994427_903097961_25607\actualconfig PolicyAgent_PolicyEvaluator 9/19/2011 7:56:37 AM 3172 (0x0C64)
Raising event:
instance of CCM_PolicyAgent_SettingsEvaluationComplete
ClientID = "GUID:371B6A81-1FF0-4A63-B6D2-59608A7FE672";
DateTime = "20110919145637.475000+000";
PolicyNamespace = "\\\\it-pc4871\\root\\ccm\\policy\\s_1_5_21_36134387_1236994427_903097961_25607\\actualconfig";
ProcessID = 2600;
ThreadID = 3172;
PolicyAgent_PolicyEvaluator 9/19/2011 7:56:37 AM 3172 (0x0C64)

SMS 2003 and ZFD 3.2 and/or 7.x interoperability

I'm forced to use SMS 2.0 on my ZFD 3.2 workstations, as our parent
company mandates it. So far, we've been able to cooperatively exist
together, but, I now have to upgrade to SMS 2003 (and, am also trying to
upgrade ZFD to 7.x).
Anybody have experience with SMS 2003 and the "advanced SMS client" (SMS
2.0 usese the "legacy" client)? Can I expect no issues, or...
Thanks!

Thanks, Craig!
"craig wilson" <[email protected]> wrote in message
news:pJ%kf.2300$[email protected]..
>
> I am not aware of any and but I do recall in the past there being an
> "issue"
> that Novell addressed.
> Hence if one were to appear, I presume Novell would again be willing to
> look
> at the issue and address it if it was really their issue to address.
>
>
> <[email protected]> wrote in message
> news:VY_kf.2245$[email protected]..
>> I'm forced to use SMS 2.0 on my ZFD 3.2 workstations, as our parent
>> company mandates it. So far, we've been able to cooperatively exist
>> together, but, I now have to upgrade to SMS 2003 (and, am also trying to
>> upgrade ZFD to 7.x).
>>
>> Anybody have experience with SMS 2003 and the "advanced SMS client" (SMS
>> 2.0 usese the "legacy" client)? Can I expect no issues, or...
>>
>> Thanks!
>
>

Cannot Install Adobe Flashplayer 9.0.16 Using SMS 2003

We are using SMS 2003 in an enterprise environment.
We have been unable to install Flash Player V9.0.16 using
SMS.
We had the same problem with Flash Player V8.0.24, and
finally gave up.
All other SMS packages we create install without difficulty,
including applications such as Adobe Reader 7x, MS Office 2003,
etc.
The error generated by SMS is:
The program for advertisement "MNG20107" failed ("MNG00099" -
"Adobe Flashplayer 9.0.16").
A failure exit code of 1 was returned.
User context: NT AUTHORITY\SYSTEM
Possible cause: Systems Management Server (SMS) determines
status for each program it executes. If SMS cannot find or
correlate any installation status Management Information Format
(MIF) files for the program, it uses the program's exit code to
determine status. An exit code of 1 is considered a failure.
Solution: For more information on the exit code, refer to the
documentation for the program you are distributing.
Attempts to search on the internet for an understanding of
this error have been unsuccessful.
Basically, we are looking for input from other SMS Admins who
have had problems installing Flash Player 9 with SMS, whether they
fixed it or not.
Hopefully, someone can provide some insight as to the nature
of the failure. I don't think its really SMS, as it generally
pushes other packages just fine. Only Flash seems to refuse to play
nice.
I am not interested in using Group Policy to push this
package, please start a seperate thread to have that discussion.
Thanks

I had the same question about what accounts were used in SMS
with advanced security. I was having a problem loading some
bluetooth drivers. Here's the reponce I got from an SMS list.
Do you have access to SMS R2? You can now use the custom
update tool for Adobe Flash.
You are correct about the Software Installation Account, it
is only for the legacy clients.
What kind of installer is the Bluetooth software using?
InstallShield?
If it is InstallShield (MSI based), I have had many problems
with InstallShield packages (MSI based) running under the SYSTEM
account, but it runs fine under my user account (which has Admin
rights). If this is the case take a look at this link:
http://community.macrovision.com/showthread.php?t=117720&page=3&pp=6
The information I'm refering to in the link is the following:
"Your probably referring to one of the many threads that
MichaelU and I had on this subject.
BTW I'd never read the document above. I've always followed a
simple approach with each release of InstallShield.
1) Install InstallScript MSI and use DCOMCNFG to determine
the AppID of the offending DCOM server.
2) Edit the ISSCRIPT.MSI to remove the RunAs registry value
of the AppID.
3) Edit the ISSCRIPT.MSI and add an entry to the
RemoveRegistry table in case the value has been previously seeded
out in the wild by a different install using the same version of
InstallShield.
4) Add the new MSI to my build environment"
Thanks,

Crypt acquire context failed with 0x8009000f after upgrade from sms 2003 to SCCM 2007 SP1

I've upgraded clients from SMS 2003 SP3 to SCCM 2007 SP1.
In the SCCM console some ressources are showing as not being client.
If I look on the machine, I can see that client is installed but the client cannot communicate with the management point.
CCMEXEC.log shows the following error message :
Crypt acquire context failed with 0x8009000f.
Failed to create certificate 8009000f CcmExec 21/04/2009 9:49:10 1948 (0x079C)
CCMDoCertificateMaintenance() failed (0x8009000f).
So, the issue is related to certificate
If I go to C:\documents and settings\all users\Application Data\Microsoft\Crypto\RSA\MachineKeys and delete the file begining by 19c5cf... and then restart the client the problem is solved.
Can someone explain what is happening ?
What can I do to prevent this problem
Kind regards

In Server 2008 R2 SP1 (when Pushing Out SCCM 2012 clients)
I just added another account to the security (local Administrators) for the key which starts with 19c5cf...
and restarted the SMS AGENT HOST SERVICE.
Thats also resolved the problem. (NETWORK was the only security account on the key file).

Adobe Deployment Toolkit - premiere pro CS4 with sms 2003

Hi I have followed all the Adobe Deployment Toolkit instructions and
the AdobeUberInstaller.exe will run in a command line mode fine , but
can't get it work in sms 2003.I have the program path as suggested \AdobeUberInstaller.exe but I see an error exit code of 1 on the failed install ie failed to parse command line.
Any ideas, or anyone had success with this depolyment?

I have only 12 GB. There is however a sound reason for that amount and not 24 or even more. A PC is only as good as it's weakest link. Usually that are the mechanical parts, meaning disks. And there is always a budget limitation. And there is availability of parts.
With all these restrictions, only 6 DIMM slots, and the limited choice of DDR3-10600 sticks in anything other than 2 GB sticks (just looking today I was not able to find any 4 GB sticks, apart from Kingston Value RAM in ECC edition with CL9 at triple the price of 2 GB), I considered it better to invest in disks than a long search for very expensive memory sticks.
These considerations make that the most logical amount of memory today is 12 GB and not 24 or more, at least on mobo's with only 6 DIMM slots.
Would Adobe use more than 12 GB, even up to xx GB, well I don't know, but the diminishing returns of the extra memory at very high prices make it more logical and economical to invest in a good disk setup.

Autheticating useing Cisco ACS 4.2 integrated with Active Directory 2003

How do i check that users are Autheticated useing Cisco ACS 4.2 integrated with Active Directory 2003, any one help me in this thanks

You can't actually see the user's membership from ACS. All you can do, create group-mapping under external database >> group mapping section. This would give you an option to map external (AD) group with an Internal group.The group memberrship need to be modified under Active Directory.
Once user is succussfully authenticated and learned as a dynamic user in ACS user setup database, it would be mapped with an ACS internal group based on group mapping we did.
Let me know if you have any doubts.
Regards,
Jatin

SQL Query (Migrating report from SMS 2003 and SCCM 2012R2)

Hello everyone,
I solicit you because I have to work on migrating reports from SMS 2003 and SCCM 2012 R2.
The following SQL query causes me some problems:
SELECT DISTINCT SYS.Netbios_Name0 AS Computer, (SELECT SUM(ProcAddtl.NumberOfLogicalProcessors0) FROM v_GS_Processor_Addtl0 ProcAddtl WHERE ProcAddtl.ResourceID=SYS.ResourceID) [Cores], CS.NumberOfProcessors0 AS CPU, CPU.MaxClockSpeed0 As Speed, CPU.Name0, MEMORY.TotalPhysicalMemory0/1024 AS [RAM Mb], (SELECT LDISKS.Name0 + '=' + CONVERT(varchar(15), LDISKS.Size0/1024) + ' | ' as 'data()' FROM v_GS_LOGICAL_DISK LDISKS WHERE LDISKS.ResourceID=SYS.ResourceID AND (LDISKS.Name0='C:' OR LDISKS.Name0='D:') ORDER BY LDISKS.Name0 FOR xml path('')) [Logical Disk (Gb)], (SELECT LDISKS.Name0 + '=' + CONVERT(varchar(15), LDISKS.FreeSpace0/1024) + ' | ' as 'data()' FROM v_GS_LOGICAL_DISK LDISKS WHERE LDISKS.ResourceID=SYS.ResourceID AND (LDISKS.Name0='C:' OR LDISKS.Name0='D:') ORDER BY LDISKS.Name0 FOR xml path('')) [Free Space(Gb)],CS.Manufacturer0 AS Manufacturer, CS.Model0, OS.Caption0 AS 'OS', (SELECT CONVERT(varchar(10), NIC.Index0) + '=' + NIC.IPAddress0 + ' | ' as 'data()' FROM v_GS_NETWORK_ADAPTER_CONFIGUR NIC WHERE NIC.ResourceID=SYS.ResourceID FOR xml path('')) [Network], (SELECT Count(Name0) FROM v_GS_SCSI_CONTROLLER SCSI WHERE SCSI.ResourceID=SYS.ResourceID AND SCSI.Name0 Like '%Qlogic%') [# FC HBA], INFONOYAU.RoleServeur0 AS Role, INFONOYAU.Zone0 AS Zone
FROM v_R_System SYS
LEFT JOIN v_GS_COMPUTER_SYSTEM CS ON CS.ResourceID = SYS.ResourceID
LEFT JOIN v_GS_PROCESSOR CPU ON CPU.ResourceID = SYS.ResourceID
LEFT JOIN v_GS_X86_PC_MEMORY MEMORY ON MEMORY.ResourceID = SYS.ResourceID
LEFT JOIN v_GS_OPERATING_SYSTEM OS ON OS.ResourceID = SYS.ResourceID
LEFT JOIN v_GS_Informations_Noyau0 INFONOYAU ON INFONOYAU.ResourceID = SYS.ResourceID
LEFT JOIN v_FullCollectionMembership COL ON COL.ResourceID = SYS.ResourceID
WHERE COL.CollectionID = @CollectionID ORDER BY SYS.Netbios_Name0
Can a charitable soul help me to migrate this query to a SCCM 2012R2 report?

The following SQL query causes me some problems:
Why? What's happening?
Torsten Meringer | http://www.mssccmfaq.de

System Management container already existing from SMS 2003

I am going to be introducing a new SCCM 2012 R2 server in our domain which has an existing SMS 2003 server. The first part of the SCCM 2012 R2 preparation is (from my understanding) is to create the "System Management" container using ADSIEdit
and give permission to the service account you create for SCCM.
As we already have SMS 2003 this container exists in our Active Director. Given this what is the proper procedure? Do I simply give permission for this container to the SCCM service account and that is it? What about the already existing items in this container
for our existing SMS server, will they be adversely affected or conflict with the newly created items?

Yes, simply assign permissions for your ConfigMgr 2012 site system(s) to that container. It won't touch the existing objects.
Do pay attention to overlap in boundaries, inc ase you use the boundaries for auto site assignment. See also:
http://social.technet.microsoft.com/Forums/en-US/18b93c00-1a6a-48bc-b19f-f17bfbcffb0f/sms-2003-and-sccm-2012-overlapping-boundaries?forum=configmanagerdeployment
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Cisco Smart Call Connector / Advanced Client / Server for UC500

Would like to hear from Cisco:
Is there still development in progress on Cisco Smart Call Connector, the advanced client, server and operator involving compatibility and support for Windows 8 / Outlook 2013 / and IE 10 32 and 64 bit ?
Please vote this up if interested !

jeliasoncisco wrote:Hello. I have a growing practice selling UC500 and would like to know this too. Cisco, please keep selling and developing this. Thanks a million!
Check forums here or talk to your Channel Account Manager.
Cisco doesn't care for the UC500 anymore and will not continue selling it for much longer.

Can't Push Advanced Client

I've got a computer that's is driving me nuts!
This computer is at one of my secondary sites. There are other computers at this site, and they're all working, but I can't get the Advanced Client installed on this one.
The computers appears in my All Systems collection. It has the site code for my remote site. If I try to install the client by right-clicking on the computer and selecting Install Client, I don't see any evidence that anything ever happens.
I don't ever see a .CCR file appear on the remote site server, I don't see anything in the CCM.log on the remote server, and I never see a CCMSetup or CCM file appear under sysWOW64 (I even checked System32 for good measure).
If I manually create a .CCR file and place in the ccr.box folder on the remote site server and watch the CCM.log file, I can see the .CCR get processed, but it reports "Mobile client on the target machine has the same version, and 'forced' flag is not
turned on." What might be present on this computer that would make SCCM think that the Advanced Client is installed on this computer.
I checked DNS and DHCP just to make sure this computer was the only one associated with its known IP address, but everything looks just like it should.
Site boundaries? I've checked them, but I don't see anything wrong. I've verified that this computers has an IP address within the AD site for that remote location and that the AD Site is the boundary for my SCCM Site.

Hi,
As it is only one comnputer I would log on to it and check the log files and trigger an installationen manually, it sounds like it already have the SCCM client installed but it is broken, WMI perhaps? Checking the ccmsetup.log and client.msi.log will give
you more detials, client push can fail if firewall, DNS,DHCP ,permissions, WMI corruption issues occur on the client.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Mouse Integration Incompatible w/ SMS 2003 Advanced Client

Similar Messages

Maybe you are looking for