Novell GINA removed after R2 upgrade to ConfigMgr 2012 SP1 client

I am working with a customer and we just noticed an issue when upgrading some of their SCCM 2012 SP1 clients to R2. After the upgrade, everything appears to work fine, but as soon as a restart happens, the Novell GINA is replaced by the Windows GINA.
These machines were running Windows XP SP3 with Novell Client 4.91 SP5. This did not occur when installing the ConfigMgr 2012 SP1 client originally, but appears to happen every time when the ConfigMgr client is upgraded to R2. I wouldn't have
thought the ConfigMgr 2012 R2 client upgrade would have anything to do with the GINA, but we can replicate the issue.
It's not due to Windows Updates getting installed in the background while the client is temporarily unmanaged, which was my initial thought. We ensured the policy to disable Windows Updates was correctly in place and that no updates were installed.
The only fix so far is to completely remove the Novell client and reinstall it.
Has anyone else run in to this?
Thanks!

Yes, I have seen this when we took over a group that had Novell. It was ConfigMgr 2007 at the time. We only had to keep Novell long enough to completely remove it later. So your process is correct.
http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

Similar Messages

Problem upgrading from SCOM 2012 SP1 to R2 (near impossible to uninstall SCOM agent from Management Server)

I'm trying to upgrade our SCOM 2012 SP1 environment to R2, but I have a heck of a problem getting there.
We currently have an test installation with SCOM 2012 SP1 with Management Server and Console on a single 2012 Standard server. The database are located on a remote server. The R2 setup stopped mid way through the setup, because the SCOM 2012 SP1 agent is
installed. And I could NOT remove it my any normal means. I've tried "misexec.exe /x productcode", the setup, powershell uninstall and so on. Nothing works, because the management server installation is blocking the uninstall. The uninstall says
I have to remove the management installation first. And that's not gonna happen.
I had to follow this guide to finally getting through the setup: http://www.opsman.co.za/forcibly-removing-a-scom-agent-that-cannot-be-uninstalled-by-normal-means/
In addition to searching for the agent msi install key in registry, and deleting everything. After I did this, the setup is working, and the SCOM management server, console and DB are up to date. However, the Microsoft Monitoring Agent are STILL there in
Control Panel. And this can NOT be the most healthy way of getting through the setup.
I'm about to upgrade to R2 in our production environment with 3 management servers, and I would hate to go through this sketchy process there as well. Just for the record, I have no idea why the agents are installed on our management servers.
Any of you have tips as to how I can get rid of the agents more gracefully?

Hi
Thanks for the replay guys!
None of those links touch my problem I'm afraid. I have followed the Upgrade guides you pointed to, step by step. But the setup does not Complete. There's problems during the actual software Upgrade of the management servers (3'rd step in the Upgrade page).
I've dived into the Application logs and installation logs, and as far as I can tell, it stops because it has trouble upgrading while the server has the 2012 SP1 Agent installed. I do not remember the actual error text right now, but I can get it in a few
days.
Anyhow, the setup DID move on once I removed most of the registry information of the agent installation. So. that leaves me to the conclusion that the agent IS in fact stopping the setup. Either the agent are malfunctioning, or the setup do not expect the
agent to be present on the management servers. I suspect the latter to be the the most plausible. At least until Yan Li told me this was normal.
So, I'm not sure what to think. I'm pretty much forced to remove this agents, as this is the only thing allowing me to continue the setup. At least untill I'm told otherwise. But I hate to do it this way. It's so dirty. The registry is pretty much cleaned,
but there's still Application files present, and the agent is still in the Control panel and can be started. It's not something I would like to do in our prodution environment.

ConfigMgr 2012 R2 client on Windows 7 SP1 x86 causes "Program Compatibility Assistant" to appear

After I upgraded to R2 I am seeing the message below on newly installed Windows 7 SP1 x86 machines when I go to Control Panel and open the Configuration Manager Properties and then close it. This seems to only happen on 32-bit Win7 not on 64-bit.
I have created a new package for the client from definition and I also tried building new images using my Build and Capture task sequences. In this case I get the same message on the x86 Windows 7 SP1 machine if I log on after the Build & Capture is
done. My Build And Capture sequences uses the RTM-image for Windows 7 SP1 that has been patched using Offline Servicing.
Has anyone else seen this? Everything is working normally on the clients and if I click "This control panel works correctly" the message goes away. However, if I click "Open the control panel using recommended settings" that results in
admin-rights being required to open the Configuration Manager Properties under the Control Panel.
Regards,
Carl

I just pinged the product team and they are not aware of this issue at all so please someone open a support case with CSS where the issue can be worked.
Jason | http://blog.configmgrftw.com
I'll be opening a support case first thing monday :)
Tim Nilimaa | Blog: http://infoworks.tv | Twitter: @timnilimaa
Hi Tim
How did you go with this? We're still seeing this issue migrating Windows 7 x86 machines from the ConfigMgr 2007 SP2 R3/ConfigMgr 2012 client to the ConfigMgr 2012 R2 client in multiple environments.
Cheers
Sam
Ticket opened with Microsoft Support, still no fix but I will keep you all posted.
Tim Nilimaa | Blog: http://infoworks.tv | Twitter: @timnilimaa

Leave Data Drive (D:) Untouched During Rebuild In ConfigMgr 2012 SP1 Task Sequence

Windows Server 2008 R2, ConfigMgr 2012 SP1
I'm looking for a way to put logic on a Task Sequence that will only format/wipe the OS partition during a rebuild i.e. leave the Data Partition (D: drive) untouched.
I have removed "Format And Partition Disk" task then which
option should be selected in "Apply operating system images" task.
SourabhR

Thanks Peter, Its worked for me :)
After proceeding with this approach got another block.
how could i avoid such cases as shown below where another partition is available before the boot partition. According to
Next available formatted partition option,highlighted partition will be wiped and will get the OS.
Is there any way like preflight checks (TS variable or wmi queries,conditions),so i can avoid this type of scenarios.
SourabhR

Failed to resume task sequence / ConfigMgr 2012 SP1 vs. R2

We have two configMgr environment at customers place. A Lab Environment and production Environment. Till July 2014 both environment were at the same Version level (ConfigMgr 2012 SP1).
We create the WIM-Image in LAB to use this WIM in the production. There were no problems till yet. Some months before we updated our
LAB to ConfigMgr 2012 R2 CU2. The Production is still
ConfigMgr 2012 SP1 CU3. Now if we create a new image in our LAB we can't use this Image in Production.
OSD ends after 'Setup Windows and ConfigMgr' step. There is an error:
Can't we use an captured Image from a ConfigMgr 2012 R2 environment in a ConfigMgr 2012 SP1 environment?

I am not 100% if this is really supported (even if the versions were equal). I've seen situations where you can still see references to the MP and sitecode of the test environment when having a close look at the logs (although it did not cause real issues).
Torsten Meringer | http://www.mssccmfaq.de

Upgrading from SCOM 2012 SP1 to SCOM 2012 R2 what CU do i install? CU5?

Hi,
I just upgraded from SCOM 2012 SP1 to SCOM 2012 R2. What CU version should I install? CU5?
Thanks
K

The most current CU version os SCOM 2012R2 is CU4
You can download it from
https://support.microsoft.com/kb/2906925?wa=wsignin1.0
For detail description of SCOM 2012 R2 CU4, you may refer to
http://support.microsoft.com/kb/2992020
and
http://syscentercldman.blogspot.hk/2014/12/update-of-scom-2012-r2-ur4.html
Roger

Server 2012 X64 R2 DNS Server keeps shutting down after inplace upgrade from Server 2012 X64

Hi,
ever since upgrading from Server 2012 X64 to Server 2012 R2 X64 my dns server keeps shutting down every several minutes before having to do a restart. When viewing the event log this is all I see..
The DNS Server service terminated unexpectedly. It has done this 497 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
if I look in the Application Error Log, I will also find the following:
Faulting application name: dns.exe, version: 6.3.9600.17031, time stamp: 0x530871fb
Faulting module name: dns.exe, version: 6.3.9600.17031, time stamp: 0x530871fb
Exception code: 0xc0000005
Fault offset: 0x000000000010b0e0
Faulting process id: 0x1740
Faulting application start time: 0x01cf531b2e3a7f5e
Faulting application path: C:\Windows\system32\dns.exe
Faulting module path: C:\Windows\system32\dns.exe
Report Id: 90a4ab37-bf0e-11e3-9446-003048df3f03
Faulting package full name:
Faulting package-relative application ID:
I have tried removing and then reinstalling the DNS Server role, but the same situation occurs..
thanks,

Hi,
I'm going crazy, I've upgraded my Server 2012 Standard to Server 2012 R2 Standard and now my DNS server keeps crashing since the in place upgrade. I have finally narrowed it down to it only crashes after several minutes if I load the data from
a file instead of the registry. As a test I:
-1- killed all my dns data,
-2- uninstalled the dns server role
-3- deleted the /windows/system32/dns directory
-4- reinstalled the DNS server role
-5- used the wizard to create a DNS server and a forward zone.
everything works okay, no crashes, then I change the advanced propertied of the DNS server to load from file, restart the DNS server and once again it crashes every 2 minutes..
Please help, this is killing me..
thanks in advance..

SMS_Exec service crashing repeatedly after upgrade from SCCM 2012 SP1 to 2012R2

SCCM 2012R2 is running on 2008R2 in the primary site. After the upgrade to R2 we noticed that none of the stats or collection memberships were updating. We also couldn't manually run summerization on any deployments.
We started digging through logs and looking at some of the threads on there with similar issues but couldn't see any issues with inbox contents or any of the other suggested fixes. We tried repairing .NET but that didn't help.
If anyone can help guide us in the right direction it would be greatly appreciated. I've included the crash.log below.
EXCEPTION INFORMATION
Time = 12/30/2013 13:08:43.990
Service name = SMS_EXECUTIVE
Thread name = SMS_ALERT_NOTIFICATION
Executable = C:\Program Files\Microsoft Configuration Manager\bin\x64\smsexec.exe
Process ID = 3368 (0xd28)
Thread ID = 4684 (0x124c)
Instruction address = 0000000077B33290
Exception = c0000005 (EXCEPTION_ACCESS_VIOLATION)
Description = "The thread tried to read from the virtual address 0000000000BA2D28 for which it does not have the appropriate access."
Raised inside CService mutex = No
CService mutex description = ""
LOADED MODULES
Module BaseAddr Size File Version Product Version Debug Symbols Full Path To Module Full Path To Debug Symbols
===========================================================================================================================================================================
C:\Windows\WinSxS\amd64_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_044aad0bab1eb146\mfc90.dll 0000000053FD0000 004e4000 9.0.30729.6161 9.0.30729.6161 Symbols Load Failed C:\Windows\WinSxS\amd64_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_044aad0bab1eb146\mfc90.dll
C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251\MSVCR90.dll 000000006E0B0000 000a3000 9.0.30729.6161 9.0.30729.6161 DLL Exports Only C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251\MSVCR90.dll
C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251\MSVCP90.dll 000000006E7D0000 000d3000 9.0.30729.6161 9.0.30729.6161 DLL Exports Only C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251\MSVCP90.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\basesvr.dll 0000000070220000 00393000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\basesvr.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseobj.dll 00000000705C0000 001e7000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\baseobj.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll 00000000707B0000 0014a000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\mfc100.dll 0000000070900000 0055d000 10.0.40219.1 10.0.40219.1 Symbols Load Failed C:\Program Files\Microsoft Configuration Manager\bin\x64\mfc100.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\MSVCR100.dll 0000000071780000 000d2000 10.0.40219.1 10.0.40219.1 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\MSVCR100.dll
C:\Windows\system32\MSVCP100.dll 0000000072840000 00098000 10.0.40219.1 10.0.40219.1 DLL Exports Only C:\Windows\system32\MSVCP100.dll
C:\Windows\system32\security.dll 0000000072B70000 00003000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\security.dll
C:\Windows\system32\odbcint.dll 0000000073020000 00038000 6.1.7600.16385 6.1.7600.16385 Symbols Load Failed C:\Windows\system32\odbcint.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\amtproxymgr.dll 0000000073200000 00024000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\amtproxymgr.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\aikbmgr.dll 0000000073230000 00016000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\aikbmgr.dll
C:\Windows\system32\sqlncli11.dll 0000000073470000 00353000 2011.110.2100.60 11.0.2100.60 DLL Exports Only C:\Windows\system32\sqlncli11.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\SMSSVREH.DLL 0000000073A70000 0000f000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\SMSSVREH.DLL
C:\Program Files\Microsoft Configuration Manager\bin\x64\MFC100ENU.DLL 0000000074130000 0000d000 10.0.40219.1 10.0.40219.1 Symbols Load Failed C:\Program Files\Microsoft Configuration Manager\bin\x64\MFC100ENU.DLL
C:\Program Files\Microsoft Configuration Manager\bin\x64\LibRDC.dll 0000000074140000 00029000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\LibRDC.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\basesql.dll 0000000074170000 0004c000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\basesql.dll
C:\Windows\system32\1033\SQLNCLIR11.RLL 0000000074270000 00038000 2011.110.2100.60 11.0.2100.60 Symbols Load Failed C:\Windows\system32\1033\SQLNCLIR11.RLL
C:\Windows\WinSxS\amd64_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_01c9581e60cbee58\MFC90ENU.DLL 0000000074930000 0000d000 9.0.30729.6161 9.0.30729.6161 Symbols Load Failed C:\Windows\WinSxS\amd64_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_01c9581e60cbee58\MFC90ENU.DLL
C:\Windows\system32\USER32.dll 0000000077400000 000fa000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\USER32.dll
C:\Windows\system32\kernel32.dll 0000000077500000 0011f000 6.1.7601.18229 6.1.7601.18229 DLL Exports Only C:\Windows\system32\kernel32.dll
C:\Windows\SYSTEM32\ntdll.dll 0000000077AE0000 001a9000 6.1.7601.18247 6.1.7601.18247 DLL Exports Only C:\Windows\SYSTEM32\ntdll.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\smsexec.exe 000000013FDA0000 0001f000 5.0.7804.1000 5.0.7804.1000 Symbols Load Failed C:\Program Files\Microsoft Configuration Manager\bin\x64\smsexec.exe
C:\Windows\system32\dbghelp.dll 000007FEE3340000 00125000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\dbghelp.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\AmtUtil.dll 000007FEF40A0000 00174000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\AmtUtil.dll
C:\Windows\system32\comsvcs.dll 000007FEF4400000 001b0000 2001.12.8530.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\comsvcs.dll
C:\Windows\system32\MTXDM.DLL 000007FEF45B0000 0000e000 2001.12.8530.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\MTXDM.DLL
C:\Windows\system32\framedynos.dll 000007FEF5670000 0004c000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\framedynos.dll
C:\Windows\system32\ODBC32.dll 000007FEF56C0000 000b1000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\ODBC32.dll
C:\Windows\system32\CLUSAPI.DLL 000007FEF5800000 00050000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\CLUSAPI.DLL
C:\Windows\system32\RESUTILS.DLL 000007FEF5950000 00019000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\RESUTILS.DLL
C:\Windows\system32\MSIMG32.dll 000007FEF5A00000 00007000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\MSIMG32.dll
C:\Windows\system32\BROWCLI.DLL 000007FEF5FC0000 00012000 6.1.7601.17887 6.1.7601.17887 DLL Exports Only C:\Windows\system32\BROWCLI.DLL
C:\Windows\system32\webio.dll 000007FEF6090000 00064000 6.1.7601.17725 6.1.7601.17725 Symbols Load Failed C:\Windows\system32\webio.dll
C:\Windows\system32\WINHTTP.dll 000007FEF6100000 00071000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\WINHTTP.dll
C:\Windows\System32\msxml6.dll 000007FEF61B0000 001f1000 6.30.7601.17988 6.30.7601.17988 DLL Exports Only C:\Windows\System32\msxml6.dll
C:\Windows\system32\cscapi.dll 000007FEF8990000 0000f000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\cscapi.dll
C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_a4d3b9377117c3df\COMCTL32.dll 000007FEF89E0000 000a0000 5.82.7601.18201 6.1.7601.18201 DLL Exports Only C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_a4d3b9377117c3df\COMCTL32.dll
C:\Windows\system32\WSOCK32.dll 000007FEF96A0000 00009000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\WSOCK32.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\NotiCtrl.dll 000007FEF9750000 00017000 5.0.7804.1000 5.0.7804.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\NotiCtrl.dll
C:\Windows\system32\MPR.dll 000007FEF9D30000 00018000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\MPR.dll
C:\Windows\system32\adsldpc.dll 000007FEF9D70000 0003d000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\adsldpc.dll
C:\Windows\system32\ACTIVEDS.dll 000007FEF9DB0000 00046000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\ACTIVEDS.dll
C:\Windows\system32\SAMCLI.DLL 000007FEFA930000 00014000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\SAMCLI.DLL
C:\Windows\system32\ntdsapi.dll 000007FEFA9D0000 00027000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\ntdsapi.dll
C:\Windows\system32\rasadhlp.dll 000007FEFAA00000 00008000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\rasadhlp.dll
C:\Windows\system32\wkscli.dll 000007FEFADA0000 00015000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\wkscli.dll
C:\Windows\system32\NETAPI32.dll 000007FEFADC0000 00016000 6.1.7601.17887 6.1.7601.17887 DLL Exports Only C:\Windows\system32\NETAPI32.dll
C:\Windows\System32\fwpuclnt.dll 000007FEFAFF0000 00053000 6.1.7601.18283 6.1.7601.18283 DLL Exports Only C:\Windows\System32\fwpuclnt.dll
C:\Windows\system32\WINNSI.DLL 000007FEFB100000 0000b000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\WINNSI.DLL
C:\Windows\system32\IPHLPAPI.DLL 000007FEFB140000 00027000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\IPHLPAPI.DLL
C:\Program Files\Microsoft Configuration Manager\bin\x64\AmtInstFileUtil.dll 000007FEFBC30000 00031000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\AmtInstFileUtil.dll
C:\Program Files\Microsoft Configuration Manager\bin\x64\Certificate.dll 000007FEFBC70000 00015000 5.0.7958.1000 5.0.7958.1000 DLL Exports Only C:\Program Files\Microsoft Configuration Manager\bin\x64\Certificate.dll
C:\Windows\system32\DSROLE.DLL 000007FEFBDB0000 0000c000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\DSROLE.DLL
C:\Windows\system32\ATL.DLL 000007FEFBDD0000 00019000 3.5.2284.0 6.5.0.2284 DLL Exports Only C:\Windows\system32\ATL.DLL
C:\Windows\system32\dwmapi.dll 000007FEFC320000 00018000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\dwmapi.dll
C:\Windows\system32\UxTheme.dll 000007FEFC880000 00056000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\UxTheme.dll
C:\Windows\system32\WTSAPI32.dll 000007FEFCEB0000 00011000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\WTSAPI32.dll
C:\Windows\system32\VERSION.dll 000007FEFD080000 0000c000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\VERSION.dll
C:\Windows\System32\wshtcpip.dll 000007FEFD150000 00007000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\System32\wshtcpip.dll
C:\Windows\system32\schannel.DLL 000007FEFD360000 00057000 6.1.7601.18270 6.1.7601.18270 DLL Exports Only C:\Windows\system32\schannel.DLL
C:\Windows\system32\rsaenh.dll 000007FEFD3E0000 00047000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\rsaenh.dll
C:\Windows\system32\credssp.dll 000007FEFD430000 0000a000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\credssp.dll
C:\Windows\system32\bcryptprimitives.dll 000007FEFD480000 0004c000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\bcryptprimitives.dll
C:\Windows\system32\DNSAPI.dll 000007FEFD560000 0005b000 6.1.7601.17570 6.1.7601.17570 DLL Exports Only C:\Windows\system32\DNSAPI.dll
C:\Windows\system32\kerberos.DLL 000007FEFD670000 000b4000 6.1.7601.17926 6.1.7601.17926 DLL Exports Only C:\Windows\system32\kerberos.DLL
C:\Windows\system32\LOGONCLI.DLL 000007FEFD780000 00030000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\LOGONCLI.DLL
C:\Windows\system32\msv1_0.DLL 000007FEFD7B0000 00051000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\msv1_0.DLL
C:\Windows\system32\netutils.dll 000007FEFD850000 0000c000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\netutils.dll
C:\Windows\System32\wship6.dll 000007FEFD860000 00007000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\System32\wship6.dll
C:\Windows\system32\mswsock.dll 000007FEFD870000 00055000 6.1.7601.18254 6.1.7601.18254 DLL Exports Only C:\Windows\system32\mswsock.dll
C:\Windows\system32\bcrypt.dll 000007FEFD900000 00022000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\bcrypt.dll
C:\Windows\system32\ncrypt.dll 000007FEFD930000 0004d000 6.1.7601.18270 6.1.7601.18270 DLL Exports Only C:\Windows\system32\ncrypt.dll
C:\Windows\system32\CRYPTSP.dll 000007FEFD9C0000 00017000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\CRYPTSP.dll
C:\Windows\system32\srvcli.dll 000007FEFD9E0000 00023000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\srvcli.dll
C:\Windows\system32\cryptdll.dll 000007FEFDAF0000 00014000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\cryptdll.dll
C:\Windows\system32\secur32.dll 000007FEFDB10000 0000b000 6.1.7601.18270 6.1.7601.18270 DLL Exports Only C:\Windows\system32\secur32.dll
C:\Windows\system32\SspiCli.dll 000007FEFDDA0000 00025000 6.1.7601.18270 6.1.7601.18270 DLL Exports Only C:\Windows\system32\SspiCli.dll
C:\Windows\system32\CRYPTBASE.dll 000007FEFDE30000 0000f000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\CRYPTBASE.dll
C:\Windows\system32\RpcRtRemote.dll 000007FEFDF20000 00014000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\RpcRtRemote.dll
C:\Windows\system32\profapi.dll 000007FEFDF40000 0000f000 6.1.7600.16385 6.1.7600.16385 Symbols Load Failed C:\Windows\system32\profapi.dll
C:\Windows\system32\MSASN1.dll 000007FEFDFE0000 0000f000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\MSASN1.dll
C:\Windows\system32\KERNELBASE.dll 000007FEFE0B0000 0006b000 6.1.7601.18229 6.1.7601.18229 DLL Exports Only C:\Windows\system32\KERNELBASE.dll
C:\Windows\system32\WINTRUST.dll 000007FEFE120000 0003a000 6.1.7601.18205 6.1.7601.18205 DLL Exports Only C:\Windows\system32\WINTRUST.dll
C:\Windows\system32\CRYPT32.dll 000007FEFE160000 0016c000 6.1.7601.18277 6.1.7601.18277 DLL Exports Only C:\Windows\system32\CRYPT32.dll
C:\Windows\system32\CLBCatQ.DLL 000007FEFE310000 00099000 2001.12.8530.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\CLBCatQ.DLL
C:\Windows\system32\ole32.dll 000007FEFE430000 00203000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\ole32.dll
C:\Windows\system32\SHELL32.dll 000007FEFE640000 00d88000 6.1.7601.18222 6.1.7601.18222 DLL Exports Only C:\Windows\system32\SHELL32.dll
C:\Windows\system32\WLDAP32.dll 000007FEFF3D0000 00052000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\WLDAP32.dll
C:\Windows\system32\USP10.dll 000007FEFF430000 000c9000 1.626.7601.18009 1.626.7601.18009 DLL Exports Only C:\Windows\system32\USP10.dll
C:\Windows\system32\COMDLG32.dll 000007FEFF500000 00097000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\COMDLG32.dll
C:\Windows\system32\LPK.dll 000007FEFF780000 0000e000 6.1.7601.18177 6.1.7601.18177 DLL Exports Only C:\Windows\system32\LPK.dll
C:\Windows\system32\IMM32.DLL 000007FEFF790000 0002e000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\IMM32.DLL
C:\Windows\system32\NSI.dll 000007FEFF7C0000 00008000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\NSI.dll
C:\Windows\system32\ADVAPI32.dll 000007FEFF7D0000 000db000 6.1.7601.18247 6.1.7601.18247 DLL Exports Only C:\Windows\system32\ADVAPI32.dll
C:\Windows\system32\GDI32.dll 000007FEFF8B0000 00067000 6.1.7601.18275 6.1.7601.18275 DLL Exports Only C:\Windows\system32\GDI32.dll
C:\Windows\system32\IMAGEHLP.DLL 000007FEFF920000 00019000 6.1.7601.18288 6.1.7601.18288 DLL Exports Only C:\Windows\system32\IMAGEHLP.DLL
C:\Windows\system32\MSCTF.dll 000007FEFF940000 00109000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\system32\MSCTF.dll
C:\Windows\system32\OLEAUT32.dll 000007FEFFA50000 000d7000 6.1.7601.17676 6.1.7601.17676 DLL Exports Only C:\Windows\system32\OLEAUT32.dll
C:\Windows\system32\RPCRT4.dll 000007FEFFB30000 0012d000 6.1.7601.18205 6.1.7601.18205 DLL Exports Only C:\Windows\system32\RPCRT4.dll
C:\Windows\system32\WS2_32.dll 000007FEFFC60000 0004d000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\WS2_32.dll
C:\Windows\SYSTEM32\sechost.dll 000007FEFFCB0000 0001f000 6.1.7600.16385 6.1.7600.16385 DLL Exports Only C:\Windows\SYSTEM32\sechost.dll
C:\Windows\system32\SHLWAPI.dll 000007FEFFCD0000 00071000 6.1.7601.17514 6.1.7601.17514 DLL Exports Only C:\Windows\system32\SHLWAPI.dll
C:\Windows\system32\msvcrt.dll 000007FEFFD50000 0009f000 7.0.7601.17744 6.1.8638.17744 DLL Exports Only C:\Windows\system32\msvcrt.dll
STACK TRACE FOR SMS_EXECUTIVE THREAD 4516 (0x11a4) AT 12/30/2013 13:08:44.120
CS: 0033 RIP: 0000000077B0C541 EFLAGS: 00000246
SS: 002b RSP: 0000000001ABFB30 RBP: 0000000000000000
DS: 0000 ES: 0000 FS: 0000 GS: 0000
RAX: 0000000000000000 RDX: 0000000000C06BD0
RBX: 0000000000000000 RCX: 0000000000C0F960
RSI: 0000000000000000 RDI: 0000000000000000
R8: 000007FFFFFD6000 R9: 0000000000000004
R10: 0000000000000000 R11: 0000000000000043
R12: 0000000000000000 R13: 0000000000000000
R14: 0000000000000000 R15: 0000000000000000
Module Address Offset Function + Displacement # Params Possible Values Of First Four Params Decorated Function Name
================================================================================================================================================================================================================================
C:\Windows\SYSTEM32\ntdll.dll 0000000077B315FA 000515fa ZwDelayExecution() + 10 bytes Unknown 00000000 00000000 00000000 00000000 ZwDelayExecution
C:\Windows\system32\KERNELBASE.dll 000007FEFE0B1203 00001203 SleepEx() + 179 bytes Unknown 00000000 00000000 00000000 00000000 SleepEx
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll 00000000707F51A1 000451a1 CService::ProceedIfNotHandlingException() + 29 bytes Unknown 00000000 00000000 00000000 00000000 ?ProceedIfNotHandlingException@CService@@CAXXZ
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll 00000000707F3844 00043844 CService::Yield() + 44 bytes Unknown 00000000 00000000 00000000 00000000 ?Yield@CService@@SAKHK@Z
C:\Program Files\Microsoft Configuration Manager\bin\x64\smsexec.exe 000000013FDACC86 0000cc86 Unknown Unknown 00000000 00000000 00000000 00000000 Unknown
C:\Program Files\Microsoft Configuration Manager\bin\x64\smsexec.exe 000000013FDB08CA 000108ca Unknown Unknown 00000000 00000000 00000000 00000000 Unknown
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll 00000000707F40F2 000440f2 CService::_WorkerThread() + 54 bytes Unknown 00000000 00000000 00000000 00000000 ?_WorkerThread@CService@@CAKPEAX@Z
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll 00000000707F3F60 00043f60 CService::_NewThreadWrapper() + 28 bytes Unknown 00000000 00000000 00000000 00000000 ?_NewThreadWrapper@CService@@CAKPEAX@Z
C:\Windows\system32\kernel32.dll 000000007751652D 0001652d BaseThreadInitThunk() + 13 bytes Unknown 00000000 00000000 00000000 00000000 BaseThreadInitThunk
C:\Windows\SYSTEM32\ntdll.dll 0000000077B0C541 0002c541 RtlUserThreadStart() + 33 bytes Unknown 00000000 00000000 00000000 00000000 RtlUserThreadStart
WARNING: The stack could not be completely unwound. This is usually due to a
limitation in the stack unwinding algorithm, but it can also happen if the stack
itself was corrupted.
STACK TRACE FOR SMS_ALERT_NOTIFICATION THREAD 4684 (0x124c) AT 12/30/2013 13:08:43.990
CS: 0033 RIP: 0000000077B0C541 EFLAGS: 00010202
SS: 002b RSP: 0000000002F2FCC0 RBP: 0000000000000000
DS: 002b ES: 002b FS: 0053 GS: 002b
RAX: 000000125A55DA38 RDX: 00000000023123E0
RBX: 0000000000000000 RCX: 000000FFFFFFFFFF
RSI: 0000000000000000 RDI: 0000000000000000
R8: 00000000023123F0 R9: 000007BC01BA00BC
R10: 6F626E695C554946 R11: 00000000004DAB18
R12: 0000000000000000 R13: 0000000000000000
R14: 0000000000000000 R15: 0000000000000000
Module Address Offset Function + Displacement # Params Possible Values Of First Four Params Decorated Function Name
================================================================================================================================================================================================================================
C:\Windows\SYSTEM32\ntdll.dll 0000000077B33290 00053290 RtlFreeHeap() + 208 bytes Unknown 00000000 00000000 00000000 00000000 RtlFreeHeap
C:\Windows\system32\kernel32.dll 000000007752300A 0002300a HeapFree() + 10 bytes Unknown 00000000 00000000 00000000 00000000 HeapFree
C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251\MSVCR90.dll 000000006E0FCABC 0004cabc free() + 28 bytes Unknown 00000000 00000000 00000000 00000000 free
C:\Program Files\Microsoft Configuration Manager\bin\x64\NotiCtrl.dll 000007FEF97560D6 000060d6 ConnectToShare() + 4254 bytes Unknown 00000000 00000000 00000000 00000000 ConnectToShare
C:\Program Files\Microsoft Configuration Manager\bin\x64\NotiCtrl.dll 000007FEF97569FF 000069ff ConnectToShare() + 6599 bytes Unknown 00000000 00000000 00000000 00000000 ConnectToShare
C:\Program Files\Microsoft Configuration Manager\bin\x64\NotiCtrl.dll 000007FEF975AC17 0000ac17 ThreadMain() + 9579 bytes Unknown 00000000 00000000 00000000 00000000 ThreadMain
C:\Program Files\Microsoft Configuration Manager\bin\x64\NotiCtrl.dll 000007FEF975B00D 0000b00d ThreadMain() + 10593 bytes Unknown 00000000 00000000 00000000 00000000 ThreadMain
C:\Program Files\Microsoft Configuration Manager\bin\x64\NotiCtrl.dll 000007FEF97587A0 000087a0 ThreadMain() + 244 bytes Unknown 00000000 00000000 00000000 00000000 ThreadMain
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll 00000000707F3F60 00043f60 CService::_NewThreadWrapper() + 28 bytes Unknown 00000000 00000000 00000000 00000000 ?_NewThreadWrapper@CService@@CAKPEAX@Z
C:\Windows\system32\kernel32.dll 000000007751652D 0001652d BaseThreadInitThunk() + 13 bytes Unknown 00000000 00000000 00000000 00000000 BaseThreadInitThunk
C:\Windows\SYSTEM32\ntdll.dll 0000000077B0C541 0002c541 RtlUserThreadStart() + 33 bytes Unknown 00000000 00000000 00000000 00000000 RtlUserThreadStart
WARNING: The stack could not be completely unwound. This is usually due to a
limitation in the stack unwinding algorithm, but it can also happen if the stack
itself was corrupted.
STACK TRACE FOR SMS_AMT_PROXY_COMPONENT THREAD 7724 (0x1e2c) AT 12/30/2013 13:08:44.150
CS: 0033 RIP: 0000000077B0C541 EFLAGS: 00000246
SS: 002b RSP: 00000000030BFC00 RBP: 0000000000000000
DS: 0000 ES: 0000 FS: 0000 GS: 0000
RAX: 0000000000C3CE30 RDX: 000000000000008C
RBX: 0000000000000000 RCX: 0000000000120000
RSI: 0000000000000000 RDI: 0000000000000000
R8: 0000000000C3CE20 R9: 0000000000C3CE30
R10: 0000000000000002 R11: 0000000000C3CE78
R12: 0000000000000000 R13: 0000000000000000
R14: 0000000000000000 R15: 0000000000000000
Module Address Offset Function + Displacement # Params Possible Values Of First Four Params Decorated Function Name
================================================================================================================================================================================================================================
C:\Windows\SYSTEM32\ntdll.dll 0000000077B3168A 0005168a NtQueryAttributesFile() + 10 bytes Unknown 00000000 00000000 00000000 00000000 NtQueryAttributesFile
C:\Windows\system32\KERNELBASE.dll 000007FEFE0B32C8 000032c8 GetFileAttributesW() + 120 bytes Unknown 00000000 00000000 00000000 00000000 GetFileAttributesW
C:\Windows\system32\KERNELBASE.dll 000007FEFE0B9784 00009784 GetFileAttributesA() + 68 bytes Unknown 00000000 00000000 00000000 00000000 GetFileAttributesA
C:\Program Files\Microsoft Configuration Manager\bin\x64\AmtUtil.dll 000007FEF40F152C 0005152c CAMTInboxManager::InitializeSiteComponentInbox() + 436 bytes Unknown 00000000 00000000 00000000 00000000 ?InitializeSiteComponentInbox@CAMTInboxManager@@QEAAJPEBD0@Z
C:\Program Files\Microsoft Configuration Manager\bin\x64\amtproxymgr.dll 000000007321107F 0001107f ThreadMain() + 9075 bytes Unknown 00000000 00000000 00000000 00000000 ThreadMain
C:\Program Files\Microsoft Configuration Manager\bin\x64\amtproxymgr.dll 0000000073213379 00013379 ThreadMain() + 18029 bytes Unknown 00000000 00000000 00000000 00000000 ThreadMain
C:\Program Files\Microsoft Configuration Manager\bin\x64\amtproxymgr.dll 000000007320DF0C 0000df0c CCertificateHashList::operator=() + 15580 bytes Unknown 00000000 00000000 00000000 00000000 ??4CCertificateHashList@@QEAAAEAV0@AEBV0@@Z
C:\Program Files\Microsoft Configuration Manager\bin\x64\amtproxymgr.dll 000000007320ECB5 0000ecb5 CAMTInboxManager::operator=() + 137 bytes Unknown 00000000 00000000 00000000 00000000 ??4CAMTInboxManager@@QEAAAEAV0@AEBV0@@Z
C:\Program Files\Microsoft Configuration Manager\bin\x64\amtproxymgr.dll 000000007320ED15 0000ed15 ThreadMain() + 9 bytes Unknown 00000000 00000000 00000000 00000000 ThreadMain
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll 00000000707F3F60 00043f60 CService::_NewThreadWrapper() + 28 bytes Unknown 00000000 00000000 00000000 00000000 ?_NewThreadWrapper@CService@@CAKPEAX@Z
C:\Windows\system32\kernel32.dll 000000007751652D 0001652d BaseThreadInitThunk() + 13 bytes Unknown 00000000 00000000 00000000 00000000 BaseThreadInitThunk
C:\Windows\SYSTEM32\ntdll.dll 0000000077B0C541 0002c541 RtlUserThreadStart() + 33 bytes Unknown 00000000 00000000 00000000 00000000 RtlUserThreadStart
WARNING: The stack could not be completely unwound. This is usually due to a
limitation in the stack unwinding algorithm, but it can also happen if the stack
itself was corrupted.
STACK TRACE FOR SMS_AI_KB_MANAGER THREAD 2468 (0x9a4) AT 12/30/2013 13:08:44.166
CS: 0033 RIP: 0000000077B0C541 EFLAGS: 00000246
SS: 002b RSP: 0000000001E4FC90 RBP: 0000000000000000
DS: 0000 ES: 0000 FS: 0000 GS: 0000
RAX: 0000000000000000 RDX: 0000000000000080
RBX: 0000000000000000 RCX: 0000000001E4F8A0
RSI: 0000000000000000 RDI: 0000000000000000
R8: 0000000070228A40 R9: 0000000001E4F878
R10: 0000000000000001 R11: 0000000001E4F790
R12: 0000000000000000 R13: 0000000000000000
R14: 0000000000000000 R15: 0000000000000000
Module Address Offset Function + Displacement # Params Possible Values Of First Four Params Decorated Function Name
================================================================================================================================================================================================================================
C:\Windows\SYSTEM32\ntdll.dll 0000000077B3186A 0005186a NtWaitForMultipleObjects() + 10 bytes Unknown 00000000 00000000 00000000 00000000 NtWaitForMultipleObjects
C:\Windows\system32\KERNELBASE.dll 000007FEFE0B1430 00001430 GetCurrentProcess() + 64 bytes Unknown 00000000 00000000 00000000 00000000 GetCurrentProcess
C:\Windows\system32\kernel32.dll 0000000077511220 00011220 WaitForMultipleObjects() + 176 bytes Unknown 00000000 00000000 00000000 00000000 WaitForMultipleObjects
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll 00000000707F4997 00044997 CService::YieldAndWait() + 1047 bytes Unknown 00000000 00000000 00000000 00000000 ?YieldAndWait@CService@@CAKKPEBQEAXHKKHHK@Z
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll 00000000707F3B36 00043b36 CService::YieldAndWaitForMultipleObjects() + 186 bytes Unknown 00000000 00000000 00000000 00000000 ?YieldAndWaitForMultipleObjects@CService@@SAKKPEBQEAXHKHK@Z
C:\Program Files\Microsoft Configuration Manager\bin\x64\basesvr.dll 00000000703A8A88 00188a88 CSMSObjectManager::WaitForEvents() + 464 bytes Unknown 00000000 00000000 00000000 00000000 ?WaitForEvents@CSMSObjectManager@@QEAAKHPEAPEAXK@Z
C:\Program Files\Microsoft Configuration Manager\bin\x64\aikbmgr.dll 0000000073234CF7 00004cf7 Unknown Unknown 00000000 00000000 00000000 00000000 Unknown
C:\Program Files\Microsoft Configuration Manager\bin\x64\aikbmgr.dll 0000000073235BFD 00005bfd ThreadMain() + 289 bytes Unknown 00000000 00000000 00000000 00000000 ThreadMain
C:\Program Files\Microsoft Configuration Manager\bin\x64\baseutil.dll 00000000707F3F60 00043f60 CService::_NewThreadWrapper() + 28 bytes Unknown 00000000 00000000 00000000 00000000 ?_NewThreadWrapper@CService@@CAKPEAX@Z
C:\Windows\system32\kernel32.dll 000000007751652D 0001652d BaseThreadInitThunk() + 13 bytes Unknown 00000000 00000000 00000000 00000000 BaseThreadInitThunk
C:\Windows\SYSTEM32\ntdll.dll 0000000077B0C541 0002c541 RtlUserThreadStart() + 33 bytes Unknown 00000000 00000000 00000000 00000000 RtlUserThreadStart
WARNING: The stack could not be completely unwound. This is usually due to a
limitation in the stack unwinding algorithm, but it can also happen if the stack
itself was corrupted.
ATTEMPTING TO WRITE OUT A MINIDUMP...
- Successfully wrote out a minidump.

Hi,
I agree with Jason.
You'd better contact product support so that they can track the crash to see if there is a common theme
around it, thus the need for a hotfix. Or maybe there is already a hotfix for this that has not been made public yet.
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 a ConfigMgr 2012 Secondary site

Hello All,
Just to get a clarification, Is it possible to upgrade or promote an existing ConfigMgr 2012 Secondary site to a Primary Site. I didn't install any seoarate SQL server for secondary site. Am using the default SQL configuration.
Please help.
V I S H N U

I didn't install any seoarate SQL server for secondary site. Am using the default SQL configuration.
That is not true. Secondary sites require SQL Server and will automatically install SQL Server Express.
Can you please elaborate on why you are trying to do this?
Jason | http://blog.configmgrftw.com

Upgrade from SCCM 2012 SP1 CU4 to R2 Fails - Unsupported Upgrade Path

Hi everybody,
I'm currently upgrading our SCCM infrastructure to SCCM 2012 R2 after have finished with the upgrade from SCCM 2012 RTM to SP1 CU4, thus far everything works fine, but when I try to update any
of the site servers, whether CAS or Primary, I'm getting the following error message in the Prerequisites Check:
I've gone through the system requirements and prerequisites over and over again and I can assure you that every possible update, supported OS, feature set, SQL Server, check list, etc,
etc, have been followed as per the official documentation available, however I'm stuck in this point, and surely enough I haven't been able to find out a similar case.Additionally I'm adding
the ConfigMgrPrereq log (the relevant portion of it) in case someone could kindly take a look at it.
<04-25-2014 02:06:46> ******* Start Prerequisite checking. *******
<04-25-2014 02:06:47> ********************************************
<04-25-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade,
minimum supported installed build version is [7804].
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Unsupported upgrade path;    Error;
Configuration Manager has detected that one or more sites in the hierarchy are installed with a version of Configuration Manager that is not supported for upgrade.
<04-25-2014 02:07:00> INFO: This rule only apply to primary site, skip checking.
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Active Replica MP;    Passed
<04-25-2014 02:07:00> INFO: This rule only applies to primary or secondary site in hierarchy, skip checking.
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Parent site replication status;    Passed
<04-25-2014 02:07:00> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:00> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:00> ===== INFO: Prerequisite Type & Server: SQL:INFPROSCCMCDB.usersad.everis.int
=====
<04-25-2014 02:07:00> <<<RuleCategory: Access Permissions>>>
<04-25-2014 02:07:00> <<<CategoryDesc: Checking access permissions...>>>
<04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;
SQL Server sysadmin rights;    Passed
<04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;    SQL Server sysadmin rights
for reference site;    Passed
<04-25-2014 02:07:00> INFO: CheckLocalSys is Admin of <INFPROSCCMCDB.usersad.everis.int>.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Site server computer account administrative rights;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server security mode;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: OS version:601, ServicePack:1.
<04-25-2014 02:07:09> INFO: Target computer is a Windows server.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Unsupported site server operating system version for Setup;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Domain membership;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Pending system restart;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: Dependent Components>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: Return code:0, Major:10, Minor:50, BuildNum:4000
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server version;    Passed
<04-25-2014 02:07:09> INFO: Get Sql edition:Enterprise Edition.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server Edition;    Passed
<04-25-2014 02:07:09> INFO: Checking Tcp is enabled to Static port, SQL Server:INFPROSCCMCDB.usersad.everis.int,
Instance:.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server Tcp Port;    Passed
<04-25-2014 02:07:09> INFO: Checking if SQL Server memory is limited.
<04-25-2014 02:07:09> INFO: SQL Server memory is limited.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Configuration for SQL Server memory usage;    Passed
<04-25-2014 02:07:09> INFO: Checking if SQL Server memory is configured to reserve minimum memory.
<04-25-2014 02:07:09> INFO: Installing the central administration site or primary site, requires SQL
Server to reserve a minimum of 8 gigabytes (GB) of memory.
<04-25-2014 02:07:09> WARN: SQL Server minimum memory is 8000 MB.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;    SQL Server process memory allocation;
Warning;    Configuration Manager requires SQL Server to reserve a minimum of 8 gigabytes (GB) of memory for the central administration site and primary site and a minimum of 4 gigabytes (GB) for the secondary site. This memory is reserved by
using the Minimum server memory setting under Server Memory Options and is configured by using SQL Server Management Studio. For more information about how to set a fixed amount of memory, see
http://go.microsoft.com/fwlink/p/?LinkId=233759.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Case-insensitive collation on SQL Server;    Passed
<04-25-2014 02:07:09> INFO: Check Machine FQDN: <INFPROSCCMCDB.usersad.everis.int>.
<04-25-2014 02:07:09> INFO: getaddrinfo returned success.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Validate FQDN of SQL Server Computer;    Passed
<04-25-2014 02:07:09> INFO:CheckSupportedFQDNFormat <INFPROSCCMCDB.usersad.everis.int>
<04-25-2014 02:07:09> INFO: NetBIOS <INFPROSCCMCDB>
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Primary FQDN;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: Site Upgrade Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
<04-25-2014 02:07:09> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:09> ===== INFO: Prerequisite Type & Server: SDK:INFPROSCCMCMS.usersad.everis.int
=====
<04-25-2014 02:07:09> <<<RuleCategory: Access Permissions>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking access permissions...>>>
<04-25-2014 02:07:09> INFO: The rule 'Administrative rights on site system' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: The rule 'Unsupported site server operating system version for Setup' has
been run on server 'INFPROSCCMCMS.usersad.everis.int', skipped.
<04-25-2014 02:07:09> INFO: The rule 'Domain membership' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:09> INFO: Windows Cluster not found on INFPROSCCMCMS.usersad.everis.int.
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
Windows Failover Cluster;    Passed
<04-25-2014 02:07:10> INFO: The rule 'Pending system restart' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:10> <<<RuleCategory: Dependent Components>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
Windows Deployment Tools installed;    Passed
<04-25-2014 02:07:10> INFO: CheckAdkWinPeInstalled on INFPROSCCMCMS.usersad.everis.int.
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;    Windows Preinstallation Environment
installed;    Passed
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
SMS Provider machine has same domain as site server;    Passed
<04-25-2014 02:07:10> <<<RuleCategory: Site Upgrade Requirements>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
<04-25-2014 02:07:10> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:10> ***************************************************
<04-25-2014 02:07:10> ******* Prerequisite checking is completed. *******
<04-25-2014 02:07:10> ******************************************<04-25-2014 02:07:10> INFO: Updating
Prerequisite checking result into the registry
<04-25-2014 02:07:10> INFO: Connecting to INFPROSCCMCMS.usersad.everis.int registry
<04-25-2014 02:07:10> INFO: Setting registry values
If you wonder whether it might be related to this error:
-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade, minimum supported installed build version is [7804].
I confirm that this one site is a secondary one that's attached to a primary site and this log is from the CAS server, I managed to tall it and delete it from that site, but still appears listed
on the CAS management console, any idea how to force the removal of a secondary site that's attached to a primary from the CAS site when it has been removed already from said primary?
I've already tried the
Preinst /DELSITE XXX command but it only works when the site to remove it's attached to the local site and certainly not from a CAS
Finally, the version, build number and everything is correct, no idea what could be the problem, does anybody know a way to bypass this or force the re-evaluation of this rules, I've got
the impression that it's being cached somehow.
Any help would be highly appreciated,
Thank you.
Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

Hello again everybody,
I've finally managed to fix this up, in the end I had to delete those entries manually from the database as Garry suggested. After this was done the upgrade has gone through as expected with no further ado and has finalized already, now moving on to the
primary sites.
If anybody out there is facing the same issue, what I did was to delete those "stubborn" records executing the following statements over the CAS database:
DELETE
FROMServerDataWHERESiteCode='XXX'
DELETE
FROMSC_SiteDefinitionWHERESiteCode='XXX'
And this is pretty much about it. I'd recommend to take a proper backup first though as best practice.
Thank you all anyways for your answers and comments,
Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

ConfigMgr 2012 R2 Client Failes to Install on HP EliteBook laptops with Synaptics Touchpad drivers

I've come across a fairly frustrating issue that has been taking up way too much of my time that past week or so. The issue started a little after some of our larger sites were migrated from SCCM 2007 to SCCM 2012. I started getting complaints that one of
our technical workstations (HP 8770w) was not deploying properly. I started investigating the issue and the problem involved the removal of the old ConfigMgr 2007 client and install of the new SCCM 2012 R2 client.
The Windows 7 x64 OS WIM that I am using is one that was migrated from the 07 to 2012 environment and it has been working fine. During the Setup Windows and ConfigMgr step the old client is removed and the new one for the 2012 environment installs. There
has not been any issues with this, but I feel something has changed now that we are deploying the 2012 R2 client.
Back to the issue, what happens is that the ConfigMgr client fails to uninstall the old client. Looking in the client.msi_uninstall file you will see that it is unable to locate a couple of SCCM 2007 configmgr client patches that were installed so it can
uninstall it. I get the "Couldn't find local patch ''. Looking for it at its source." line in the uninstall file. When I look for that under HKEY_CLASSES_ROOT\Installer\Patches the ENTIRE directory structure is empty. There is not a single item
listed under patches.
Since the only thing that happens in between the pushing down of the WIM and installing the configmgr client is the drivers that is where I started to look. I started over with the basics (disk and network driver) and it was able to complete the OSD process
(like the other 30+ models we currently support). I added drivers one by one having the system re-image each time. When I got to the Synaptics TouchPad drivers the issue would return. I've tried around 5 different drivers offered from the vendor and they
all result in the same behavior.
I'm still actively troubleshooting how to FIX this issue, but I have no idea why this is going on. I thought I would share with the community on this issue and see if anyone else has observed this VERY odd behavior.
Here is a snippet from the client.msi_uninstall log:
=== Verbose logging started: 1/15/2014 22:59:34 Build type: SHIP UNICODE 5.00.7601.00 Calling process: D:\_SMSTaskSequence\OSD\GAS000EF\ccmsetup.exe ===
MSI (c) (6C:BC) [22:59:34:264]: Resetting cached policy values
MSI (c) (6C:BC) [22:59:34:264]: Machine policy value 'Debug' is 0
MSI (c) (6C:BC) [22:59:34:264]: ******* RunEngine:
           ******* Product: {2609EDF1-34C4-4B03-B634-55F3B3BC4931}
           ******* Action:
           ******* CommandLine: **********
MSI (c) (6C:BC) [22:59:34:264]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (6C:BC) [22:59:34:264]: Grabbed execution mutex.
MSI (c) (6C:BC) [22:59:34:264]: Cloaking enabled.
MSI (c) (6C:BC) [22:59:34:264]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (6C:BC) [22:59:34:264]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (00:80) [22:59:34:264]: Running installation inside multi-package transaction {2609EDF1-34C4-4B03-B634-55F3B3BC4931}
MSI (s) (00:80) [22:59:34:264]: Grabbed execution mutex.
MSI (s) (00:D4) [22:59:34:264]: Resetting cached policy values
MSI (s) (00:D4) [22:59:34:264]: Machine policy value 'Debug' is 0
MSI (s) (00:D4) [22:59:34:264]: ******* RunEngine:
           ******* Product: {2609EDF1-34C4-4B03-B634-55F3B3BC4931}
           ******* Action:
           ******* CommandLine: **********
MSI (s) (00:D4) [22:59:34:264]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (00:D4) [22:59:34:405]: SRSetRestorePoint skipped for this transaction.
MSI (s) (00:D4) [22:59:34:405]: End dialog not enabled
MSI (s) (00:D4) [22:59:34:405]: Original package ==> C:\Windows\Installer\b8ba.msi
MSI (s) (00:D4) [22:59:34:405]: Package we're running from ==> C:\Windows\Installer\b8ba.msi
MSI (s) (00:D4) [22:59:34:405]: APPCOMPAT: Uninstall Flags override found.
MSI (s) (00:D4) [22:59:34:405]: APPCOMPAT: Uninstall VersionNT override found.
MSI (s) (00:D4) [22:59:34:405]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (s) (00:D4) [22:59:34:405]: APPCOMPAT: looking for appcompat database entry with ProductCode '{2609EDF1-34C4-4B03-B634-55F3B3BC4931}'.
MSI (s) (00:D4) [22:59:34:405]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (00:D4) [22:59:34:420]: MSCOREE not loaded loading copy from system32
MSI (s) (00:D4) [22:59:34:420]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
MSI (s) (00:D4) [22:59:34:420]: Couldn't find local patch ''. Looking for it at its source.
MSI (s) (00:D4) [22:59:34:420]: Resolving Patch source.
MSI (s) (00:D4) [22:59:34:420]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (00:D4) [22:59:34:420]: User policy value 'DisableMedia' is 0
MSI (s) (00:D4) [22:59:34:420]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Looking for sourcelist for product {D478B8EE-EE0A-4004-980B-4D55533EE3C2}
MSI (s) (00:D4) [22:59:34:420]: Note: 1: 1706 2: {D478B8EE-EE0A-4004-980B-4D55533EE3C2} 3:
MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Failed to resolve source
MSI (s) (00:D4) [22:59:34:420]: Searching provided command line patches for patch code {D478B8EE-EE0A-4004-980B-4D55533EE3C2}
MSI (s) (00:D4) [22:59:34:420]: Could not find source for missing patch {D478B8EE-EE0A-4004-980B-4D55533EE3C2} -- orphaning this patch
MSI (s) (00:D4) [22:59:34:420]: Couldn't find local patch ''. Looking for it at its source.
MSI (s) (00:D4) [22:59:34:420]: Resolving Patch source.
MSI (s) (00:D4) [22:59:34:420]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Looking for sourcelist for product {599B62C0-F1BE-4FE8-80D9-36937D5DDBFE}
MSI (s) (00:D4) [22:59:34:420]: Note: 1: 1706 2: {599B62C0-F1BE-4FE8-80D9-36937D5DDBFE} 3:
MSI (s) (00:D4) [22:59:34:420]: SOURCEMGMT: Failed to resolve source
MSI (s) (00:D4) [22:59:34:420]: Searching provided command line patches for patch code {599B62C0-F1BE-4FE8-80D9-36937D5DDBFE}
MSI (s) (00:D4) [22:59:34:420]: Could not find source for missing patch {599B62C0-F1BE-4FE8-80D9-36937D5DDBFE} -- orphaning this patch
MSI (s) (00:D4) [22:59:34:420]: SequencePatches starts. Product code: {2609EDF1-34C4-4B03-B634-55F3B3BC4931}, Product version: 4.00.6487.2000, Upgrade code: {252DA259-82CA-4177-B8D0-49C78937BA3E}, Product language 1033
MSI (s) (00:D4) [22:59:34:420]: SequencePatches returns success.
MSI (s) (00:D4) [22:59:34:420]: Final Patch Application Order:
MSI (s) (00:D4) [22:59:34:420]: Other Patches:
MSI (s) (00:D4) [22:59:34:420]: Internal Exception during install operation: 0xc0000005 at 0x000007FEFDBF35E1.
MSI (s) (00:D4) [22:59:34:420]: WER report disabled for silent install.
MSI (s) (00:D4) [22:59:34:420]: Internal MSI error. Installer terminated prematurely.
MSI (s) (00:D4) [22:59:34:420]: MainEngineThread is returning 1603
MSI (s) (00:80) [22:59:34:420]: No System Restore sequence number for this installation.
Unexpected Termination
MSI (s) (00:80) [22:59:34:420]: User policy value 'DisableRollback' is 0
MSI (s) (00:80) [22:59:34:420]: Machine policy value 'DisableRollback' is 0
MSI (s) (00:80) [22:59:34:420]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (00:80) [22:59:34:420]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (00:80) [22:59:34:420]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (00:80) [22:59:34:420]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (00:80) [22:59:34:420]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (00:80) [22:59:34:420]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (00:80) [22:59:34:420]: Restoring environment variables
MSI (c) (6C:BC) [22:59:34:420]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (6C:BC) [22:59:34:420]: MainEngineThread is returning 1603
=== Verbose logging stopped: 1/15/2014 22:59:34 ===

@Narcoticoo
I've not used the tool. This issue has also expanded since the original title as I'm getting the same behavior with the driver package that does not include the Touchpad driver anymore. I'm currently going back to just the network and storage driver to see
if it works or not.
However, this is the bigger issue I have:
I have an older build called Build 5.7 internally. Using that WIM and the same driver package (original one that has the Touchpad driver included) it works without issue. Never had a problem.
The new build is called Build 6.0 internally. This WIM and the same driver package has not been working at all.
We support about 35 models with our current Windows 7 x64 image and I am having the same failure issue on four different HP models. They are the 8770w, ZBook 17, Z600 and Z820. The majority of the other systems are Dell devices. Just for transparency sakes,
nothing Dell specific is in the core WIM that is captured.
So, Build 5.7 can deploy just fine on all pieces of hardware with their old driver packages. The new Build 6.0 intalls on almost every platform fine with their old driver packages. These four HP systems are nothing but trouble though. I've opened a case
with HP to see if they have noticed anything internally. I'm not too hopeful, but at least it is something. Maybe there is some odd conflict with a newer Windows patch or some odd dependency on older HP drivers. The new image has .NET 4.5.1, IE 10 and so forth.

Upgrade of scvmm 2012 sp1 to scvmm 2012 r2 fails with "Access to the path 'C:\ProgramData\VMMLogs\SetupWizard.log' is denied"

I had a working scvmm 2012 sp1 installation, and am attempting to upgrade to 2012 r2.
The old SCVMM product was removed (retaining the database), as well as ADK 8.0. I then installed ADK 8.1.
The install fails after a number of minutes with "Access to the path 'C:\ProgramData\VMMLogs\SetupWizard.log' is denied". From my reading of the log, that was the only obvious failure, and that the VMM server MSI installed successfully.
It doesn't appear to get so far as to upgrade the database.
The OS is Windows Server 2012 R2 Standard, with all updates applied. I have tried the install many times, noticed that the McAfee virus scanner was pushed to the box at some point, so I removed it, but still no dice.
12:18:58:LaunchMSI: MSI C:\Users\mscott\Desktop\mu_system_center_2012_r2_virtual_machine_manager_x86_and_x64_dvd_2913737\amd64\setup\msi\Server\vmmServer.msi succeeded.
12:18:58:Doing Postinstall task for PangaeaServer
12:18:58:ProcessInstalls: Install Item VMM management server was successful. We will launch the post process delegate.
12:19:47:Windows feature RSAT-Clustering-PowerShell already enabled, skipping
12:20:15:Windows feature WindowsStorageManagementService already enabled, skipping
12:20:41:Windows feature UpdateServices-API already enabled, skipping
12:23:31:VMMPostinstallProcessor threw an exception: Threw Exception.Type: System.UnauthorizedAccessException, Exception.Message: Access to the path 'C:\ProgramData\VMMLogs\SetupWizard.log' is denied.
12:23:31:StackTrace:   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath,
Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize, Boolean checkHost)
   at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize)
   at System.IO.StreamWriter..ctor(String path, Boolean append)
   at System.IO.File.AppendText(String path)
   at Microsoft.VirtualManager.SetupFramework.CommonLogger.Log(String trace)
   at Microsoft.VirtualManager.SetupFramework.CommonLogger.Log(LogLevel level, String trace)
   at Microsoft.VirtualManager.SetupFramework.Trc.Log(LogLevel level, String trace, Object parameter1, Object parameter2, Object parameter3)
   at Microsoft.VirtualManager.SetupFramework.Trc.LogException(LogLevel logLevel, String customMessage, Exception exception)
   at Microsoft.VirtualManager.Setup.DBConfigurator.ExecuteScript(SqlContext ctx, String fileName)
   at Microsoft.VirtualManager.Setup.DBConfigurator.UpgradeDatabaseTables()
   at Microsoft.VirtualManager.Setup.VirtualMachineManagerHelpers.CreateDB()
   at Microsoft.VirtualManager.Setup.InstallItemCustomDelegates.PangaeaServerPostinstallProcessor()
12:23:31:ProcessInstalls: Running the PostProcessDelegate returned false.
12:23:31:ProcessInstalls: Running the PostProcessDelegate for PangaeaServer failed.... This is a fatal item. Setting rollback.
12:23:31:SetProgressScreen: FinishMinorStep.
12:23:31:ProcessInstalls: Rollback is set and we are not doing an uninstall so we will stop processing installs
12:23:31:****************************************************************
12:23:31:****Starting*RollBack*******************************************
12:23:31:****************************************************************
12:23:31:SetProgressScreen: StartMinorStep.
Mark E. Scott Jr.

Perhaps relevant, perhaps not. This error shows up right after the above log snippet. I assumed it was an error with the rollback routine, but just in case, here it is:
12:23:31:SetProgressScreen: StartMinorStep.
12:23:31:ProcessInstalls: Install Item VMM management server has a Preprocessing delegate of PangaeaServerPreinstallProcessor. Launching it now.
12:23:31:GetSqlLoginName: TThe login name for the vmm server service is [DGSLAB\tfs-vmm]
12:24:49:no HAVMM name detected in DB. Doing VMM Uninstall
12:24:53:Start setspn.exe parameters -D SCVMM/tfsvmm1.dgslab.com DGSLAB\tfs-vmm
12:24:56:Start setspn.exe parameters -D SCVMM/tfsvmm1 DGSLAB\tfs-vmm
12:25:00:DBConfigurationHander.SetupAsVMMServerRole() CarmineException : Threw Exception.Type: Microsoft.VirtualManager.Utils.FailedToAcquireLockException, Exception.Message: Unable to perform the job because one or more of the selected objects are locked by
another job.
To find out which job is locking the object, in the Jobs view, group by Status, and find the running or canceling job for the object. When the job is complete, try again.
12:25:00:StackTrace:   at Microsoft.VirtualManager.Utils.CarmineObjectLock.ExecuteAcquireLockSP(CarmineObjectLockType lockType)
   at Microsoft.VirtualManager.Utils.CarmineObjectLock.AcquireLockWithRetries(CarmineObjectLockType lockType)
   at Microsoft.VirtualManager.Utils.CarmineObjectLock.AcquireLock(CarmineObjectLockType lockType, Boolean doNotWaitForLock)
   at Microsoft.VirtualManager.DB.Adhc.AgentServer..ctor(RemoteServer server, Guid serverID, Version agentVersion, VersionState agentVersionState, AgentPackageType agentPackageType, Boolean wsManOverSSL, Int32 wsManPort, Nullable`1 complianceStatusID,
Nullable`1 mostRecentTaskID, Nullable`1 mostRecentTaskUIState, Guid taskID, CarmineObjectLockType lockType)
   at Microsoft.VirtualManager.DB.Adhc.AgentServer..ctor(SqlRow row, Guid serverID, Guid taskID, CarmineObjectLockType lockType)
   at Microsoft.VirtualManager.DB.Adhc.AgentServer.<>c__DisplayClass4.<GetInstance>b__3(SqlRow row)
   at Microsoft.VirtualManager.Engine.DbAccessHelper.GetFromCommand[_RetTy,_ColumnsTy](ReadOption readOption, SqlRetryCommand cmd, GetFromCommandWorker`1 worker)
   at Microsoft.VirtualManager.Engine.DbAccessHelper.HandleReadErrors[_RetTy](DbAccessDelegate`1 func, ErrorInfo notFoundErrorInfo)
   at Microsoft.VirtualManager.DB.Adhc.AgentServer.GetOne(String computerName, GetFromCommandWorker`1 ctor, ConnectionProperties properties)
   at Microsoft.VirtualManager.Setup.DBConfigurator.SetupAsVMMServerRole(Boolean isAssociate)
12:25:00:InnerException.Type: Microsoft.VirtualManager.DB.DBCorruptionException, InnerException.Message: Unable to connect to the VMM database because the database is in an inconsistent state.
Contact an experienced SQL administrator whenever this error occurs. In some cases, it may be necessary to restore the VMM database. If the problem persists, contact Microsoft Help and Support.
12:25:00:InnerException.StackTrace:   at Microsoft.VirtualManager.DB.SqlRetryCommand.ValidateReturnValue()
   at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
   at Microsoft.VirtualManager.Utils.CarmineObjectLock.ExecuteAcquireLockSP(CarmineObjectLockType lockType)
Mark E. Scott Jr.

ConfigMgr 2012 SP1 module on runbooks servers

Let me come out the gate stating I am very new to Orchestrator and somewhat new to powershell.
I want to start testing the ConfigMgr SP1 cmdlets via runbooks. I found a blog that shows some gotchas on how to run the .Net script action which is great, however all the examples I see show importing the module from an installed management console
directory.
I am assuming that when I run a runbook that needs to reference Configmgr cmdlets that the module must imported from a local path on the runbook server(s) itself. I am really hoping that this doesnt mean I have to install the SCCM 2012 SP1
admin console on my Orchestrator Runbook Servers?
Am I just missing something obvious here? I tried copying the entire bin directory that contains the psd1 and all the associated dll's, etc. to another machine and importing the module, but unfortunately it fails with:
Import-Module : The 'C:\tmp\SCCMPowershell\ConfigurationManager.psd1' module cannot be imported because its manifest co
ntains one or more members that are not valid. The valid manifest members are ('ModuleToProcess', 'NestedModules', 'GUI
D', 'Author', 'CompanyName', 'Copyright', 'ModuleVersion', 'Description', 'PowerShellVersion', 'PowerShellHostName', 'P
owerShellHostVersion', 'CLRVersion', 'DotNetFrameworkVersion', 'ProcessorArchitecture', 'RequiredModules', 'TypesToProc
ess', 'FormatsToProcess', 'ScriptsToProcess', 'PrivateData', 'RequiredAssemblies', 'ModuleList', 'FileList', 'Functions
ToExport', 'VariablesToExport', 'AliasesToExport', 'CmdletsToExport'). Remove the members that are not valid ('HelpInfo
URI'), then try to import the module again.
At line:1 char:14
+ Import-Module <<<< .\ConfigurationManager.psd1
    + CategoryInfo          : InvalidData: (C:\tmp\SCCMPowe...ionManager.psd1:String) [Import-Module], InvalidOperatio
   nException
    + FullyQualifiedErrorId : Modules_InvalidManifestMember,Microsoft.PowerShell.Commands.ImportModuleCommand
Can someone point me in the right direction?
Thanks!!

So I partly answered my own question. The above error message was due to having Powershell 2.0 on the test machine and not 3.0 which is required. I updated the powershell version and was able to import without error (and without installing the
full admin console).
So I guess my question then comes down to what is the best practices for things like this? Certainly do not want to install admin consoles for every SC product on my runbook servers. It appears that with SCCM I can simply create a directory (standard
on all runbook servers of course) and copy the files there and import from that location. is that the preffered method for handling this?
Thanks!!

Error when trying to upgrade scsm dw 2012 sp1 to r2

Hello,
when I trying to install scsm 2012 r2 upgrade on my scsm dw server error appears.
does anyone faced and successfully resolved this problem?
regards,
Ilgar
Regards, Ilgar Khalilov.

This issue might happen if you have a space in the DW Management Group name.
Maybe this blog post from Anders Asp is helpful:
Strange error message when trying to upgrade SCSM 2012 Sp1 to SCSM 2012 R2
Andreas Baumgarten | H&D International Group

How to Upgrade Service Manager 2012 SP1 with Windows 2008 R2 to SCSM 2012 R2 with Windows 2012 R2

Hi,
We are using Service Manager 2012 SP1 UR2 with Windows 2008 R2.
I am planning to upgrade Service Manager to R2 with Windows 2012 R2. I found the steps to upgrade SCSM 2012 Sp1 to R2 but need assistance to upgrade with 2012 R2 OS.
Please suggest how to achieve the above mentioned objective.
Regards, Syed Fahad Ali

Virtualization solves this problem handily, by allowing you to create a new server to run the new program on the same hardware. it also solves the related problem of moving off unsupported hardware without changing OS or application. VMware is my personal
favorite, but Hyper-V, Xen, and VirtualBox all have similar capabilities.
Compare the cost of work and confidence in success of a upgrade, where any of thousands or millions of uncontrolled settings could cause an issue, to the cost of work and confidence in success of installing a new OS instance and configuring a known state
for the new environment.
In short, upgrades should no longer be a thing. there are just too many ways they can go wrong, and it's far too easy to create a new OS with minimal expense and effort.

Novell GINA removed after R2 upgrade to ConfigMgr 2012 SP1 client

Similar Messages

Maybe you are looking for