Random BSOD after migrated to SCCM 2012 R2 - System Endpoint Protection

We are currently experiencing random BSOD after upgrade to SCCM 2012 R2 from SCCM 2012. These BSOD are happening on our Windows 7 x64 machines. With the upgrade, we switched to System Center Endpoint Protection for the anti-virus protection and start
to notice this problem. Have anyone else experiencing the same issue? I'm trying to run adplus right now on 2 machines to try and capture the error but so far no luck. This BSOD is so random and we are getting at least 5 calls a day from users about this.
The only similarity with these BSOD is usually the user is away from keyboard and after the BSOD, System Center Endpoint cannot connect to update virus definition.
Below is a screenshot of the BSOD and it didn't create any memory dump file. We are currently running Windows 7 x64.
Message was: "STOP:
C000021a [fatal system error]. The Windows subsystem process terminate
unexpectedly with a status of 0xC0000005

- Event Type : Stopped working (APPCRASH)
      Application Name: Client Server Runtime Process
      Path:             C:\windows\system32\csrss.exe
      Event Time      : 03/22/2014 12:30:26 AM
          Application Name: csrss.exe
          Application Version: 6.1.7600.16385
          Application Timestamp: 4a5bc115
          Fault Module Name: sxs.dll
          Fault Module Version: 6.1.7601.17514
          Fault Module Timestamp: 4ce7c9cc
          Exception Code: c0000005
          Exception Offset: 0000000000011b2f
      Memory dump     : Not created

Similar Messages

SCCM 2012 R2: Forefront Endpoint protection via automatic updates only work when manually triggering automatic updat rule

Hi,
I followed this manual to configure forefront endpoint protection on clients: http://www.windows-noob.com/forums/index.php?/topic/6106-using-system-center-2012-configuration-manager-part-6-adding-the-endpoint-protection-role-configure-alerts-and-custom-antimalware-policies/
Now in short: everything works fine ... as long as I trigger the audomatic deployment rules.
Current situation:
1. ADR ran fine (3:30 this night)
2.Software update group is NOT ok
3.I run ADR manually (right click on ADR, run)
4.software update group is ok (green icon)
Then virusupdates are succesfull. This means that clients only update their virus definitions when I manually run the ADR-rule.
I'm missing something here.
Please advise.
J.
Jan Hoedt

Probably this issue: http://social.technet.microsoft.com/Forums/en-US/c6109678-785b-4c6d-9cb4-c9dfc1e34b2e/sccm-2012-automatic-deployment-rule-not-executing-updates-for-scep?forum=configmanagerapps
Iow: wsus updates were scheduled at 3, automatic update rules at 3:15, probably sync wasn't done yet so it doesn't find updates. "The day after" updates are marked as expired.
Jan Hoedt

Reports no longer work after upgrading to SCCM 2012 R2

I upgraded my SCCM 2012 SP1 environment to R2 and reports no longer work. I've removed the site role, waited a day, and added it. I've also verified the account (used by the reporting site role) has access to the DB and can logon locally. The
problem still persists. Here's a copy/paste of the error:
Microsoft.Reporting.WinForms.ReportServerException
An error has occurred during report processing. (rsProcessingAborted)
Stack Trace:
at Microsoft.Reporting.WinForms.ServerReportSoapProxy.OnSoapException(SoapException e)
at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ProxyMethodInvocation.Execute[TReturn](RSExecutionConnection connection, ProxyMethod`1 initialMethod, ProxyMethod`1 retryMethod)
at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
at Microsoft.Reporting.WinForms.ServerReport.EnsureExecutionSession()
at Microsoft.Reporting.WinForms.ServerReport.SetParameters(IEnumerable`1 parameters)
at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerWindowsForms.SetParameterValues_DoWork(Object sender, DoWorkEventArgs e)
Microsoft.Reporting.WinForms.ReportServerException
Cannot read the next data row for the dataset DataSet1. (rsErrorReadingNextDataRow)
Stack Trace:
at Microsoft.Reporting.WinForms.ServerReportSoapProxy.OnSoapException(SoapException e)
at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ProxyMethodInvocation.Execute[TReturn](RSExecutionConnection connection, ProxyMethod`1 initialMethod, ProxyMethod`1 retryMethod)
at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
at Microsoft.Reporting.WinForms.ServerReport.EnsureExecutionSession()
at Microsoft.Reporting.WinForms.ServerReport.SetParameters(IEnumerable`1 parameters)
at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerWindowsForms.SetParameterValues_DoWork(Object sender, DoWorkEventArgs e)
Microsoft.Reporting.WinForms.ReportServerException
Conversion failed when converting the nvarchar value 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXscrubbed' to data type int.
Stack Trace:
at Microsoft.Reporting.WinForms.ServerReportSoapProxy.OnSoapException(SoapException e)
at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ProxyMethodInvocation.Execute[TReturn](RSExecutionConnection connection, ProxyMethod`1 initialMethod, ProxyMethod`1 retryMethod)
at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
at Microsoft.Reporting.WinForms.ServerReport.EnsureExecutionSession()
at Microsoft.Reporting.WinForms.ServerReport.SetParameters(IEnumerable`1 parameters)
at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerWindowsForms.SetParameterValues_DoWork(Object sender, DoWorkEventArgs e)
I've tried many other TechNet solutions as well with no improvement:
http://social.technet.microsoft.com/Forums/en-US/ae08aa43-054d-47e7-99fb-c4f101962478/reports-not-working-after-upgrade-to-sccm-2012-r2-?forum=configmanagergeneral
http://social.technet.microsoft.com/Forums/en-US/77bad9b6-de0e-42d3-ae9f-e7c9d26b4330/reporting-error-after-upgrading-to-sccm-2012-r2?forum=configmanagergeneral
Any other thoughts on this?

So to be clear you have Done both the Mofcomp and Added the correct account to the Windows Authorization Access Group?
What is version of SQL are you using?
Is SSRS remote or local to CM12?
What service account are you using for SSRS?
Bases on the error message you are getting this within the console, Does the native SSRS report work? BTW I never recommend accessing the report via the console.
http://be.enhansoft.com/post/2013/09/10/Should-Configuration-Manager-SSRS-or-ASP-Reports-be-Accessed-from-the-Browser-or-the-Console.aspx
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Reports not working after upgrade to SCCM 2012 R2 -

I am having the same issue described in this post:
http://social.technet.microsoft.com/Forums/en-US/30f185ac-c34e-44ad-87eb-7d180a0d76b8/after-2012-r2-upgrade-some-sql-queries-wont-run?forum=configmanagergeneral
When running reports after upgrading from SCCM 2012 SP1 CU2 to SCCM 2012 R2 I get the following error:
An
error has occurred during report processing. (rsProcessingAborted)
Cannot
read the next data row for the dataset DataSet1. (rsErrorReadingNextDataRow)
Conversion
failed when converting the nvarchar value
'S-1-5-21-1010966800-777871707-395339515-124623' to data type int.
I have removed the Reporting Services Point and reinstalled it with no effect. All reports I try get the error listed above.
Any suggestions?

The issue has been resolved. For anyone experiencing a similar issue I will post the fix that worked for us below:
I ended up opening a PSS case and in this instance the problem was the required SQL management provider was not properly registered in WMI, which ultimately meant the reporting point upgrade/install was not able to complete successfully after the upgrade.
As a result the updated reports were not properly being redeployed to the Reporting Service Point.
To diagnose this on the Reporting Service Point look in the srsrp.log for entries indicating of an
Invalid Class, as seen in the example below:
Invalid class SMS_SRS_REPORTING_POINT 11/6/2013 5:47:12 PM 6096 (0x17D0)
Could not retrieve the reporting service name for instance 'RPSERVER' SMS_SRS_REPORTING_POINT 11/6/2013 5:47:12 PM 6096 (0x17D0)
Invalid class SMS_SRS_REPORTING_POINT 11/6/2013 5:47:12 PM 6096 (0x17D0)
Could not stop the reporting service '' SMS_SRS_REPORTING_POINT 11/6/2013 5:47:12 PM 6096 (0x17D0)
Next security configuration at [11/6/2013 5:52:12 PM] SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Root Folder exists SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Successfully checked that the SRS web service is healthy on server SERVERRP.AD.DOMAIN SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Registry change SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Waiting for changes for 1 minutes SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
SRSRP registry key change notification triggered. SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Registry change SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Waiting for changes for 1 minutes SMS_SRS_REPORTING_POINT 11/6/2013 5:47:13 PM 6096 (0x17D0)
Timed Out... SMS_SRS_REPORTING_POINT 11/6/2013 5:48:13 PM 6096 (0x17D0)
The important part is the lines saying Invalid Class and then it timing out, so the RP installation was not completed.
As mentioned earlier the WMI class that was missing or corrupt was the SQL management Provider. To re-register the class we need to compile the MOF file that is available in SQL. In our instance the command to run was:
mofcomp "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"
Once that was done, monitoring the srsrp.log shows that it could properly detect the SSRS service, stop it and start coping the updated reports and such. After a few minutes the deploy completed, and all the broken reports started working
correctly.
Hope that helps someone else.

Reporting Error After Upgrading to SCCM 2012 R2

After upgrading from SCCM 2012 SP1 CU2 to SCCM 2012 R2, some users receive an error whenever they open a report. This occurs in both the SCCM console and the SSRS web site. What's odd is not all users receive the error. In fact, for two
users with the exact same permissions, running the console on the same computer, 1 gets the error and the other doesn't. Anybody else see this or have any ideas to troubleshoot or fix it? I'm thinking this may relate to the fix for permissions
in reporting included in R2.
The error message from the console is:Microsoft.Reporting.WinForms.ReportServerException
The DefaultValue expression for the report parameter ‘UserSIDs’ contains an error: The user name or password is incorrect.
(rsRuntimeErrorInExpression)
Stack Trace:
at Microsoft.Reporting.WinForms.ServerReportSoapProxy.OnSoapException(SoapException e)
at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.ProxyMethodInvocation.Execute[TReturn](RSExecutionConnection connection, ProxyMethod`1 initialMethod, ProxyMethod`1 retryMethod)
at Microsoft.Reporting.WinForms.Internal.Soap.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
at Microsoft.Reporting.WinForms.ServerReport.EnsureExecutionSession()
at Microsoft.Reporting.WinForms.ServerReport.SetParameters(IEnumerable`1 parameters)
at Microsoft.ConfigurationManagement.AdminConsole.SrsReporting.ReportViewerWindowsForms.SetParameterValues_DoWork(Object sender, DoWorkEventArgs e)
The following error is logged in the SSRS logs:
processing!ReportServer_0-1!12d0!10/31/2013-15:28:48:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Exception of type 'Microsoft.ReportingServices.ReportProcessing.ReportProcessingException' was thrown.;

I just wanted to share my last upgrade experience with you, in case, someone is running into the same problem:
I've just upgraded to SCCM 2012 R2 CU4 (from CU3).
Guess what? It broke the Reporting, error message as above!
So I've put the computeraccount of my SCCM/SSRS server (SSRS service is running under local system account) into the WAA group, reboot - but it didn't help. Tried also the Pre-Win2000-Compat-group. Didn't help. A colleague was not experiencing the problem.
Hmmm. So what is different between our accounts?
The difference found: My account's userPrincipalName was set to the same as the sAMAccountName, but missing a domain. The account was obviously created by a bad script.
Solution 1: Delete the userPrincipalName attribute, or
Solution 2: Make the userPrincipalName complete by adding a valid domain, i.e. [email protected]: In the Active Directory Users and Computers mmc, User Properties, Account tab, select a domain for the "User logon name".
The problem seems to be only for user accounts, that are in a different domain than the SCCM server's account, i.e. server in example.com, user account in sub.example.com. Always multi-domain problems...
Thorsten Lau - IT-Lösungen http://blog.system-center.de

Migration of SCCM 2012 SP1 to SCCM 2012 R2 in a new domain.

I am wondering if it is possible to migrate objects from a SCCM 2012 SP1 server in one domain to a new SCCM 2012 R2 server in another domain ?
I read this article, but it does not state this particular combination.
http://technet.microsoft.com/en-us/library/gg682006.aspx
Thx
Thomas

For Migrate from SCCM 2012 SP1 to SCCM 2012 R2 in same environment/Domain, it's support and applicable.
But migrate to new domain, it's not support. Also you can't migrate database for new domain or object. you will need to rebuild it.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Duplicate Reports after upgrading to SCCM 2012 R2 CU1

Single Primary Site with SCCM 2012 R2 CU1.
Upgraded from SCCM 2012 SP1.
Duplicate Reports after upgrading to SCCM 2012 R2 CU1
SCCM 2012 R2 CU1
SQL 2008 SP3 CU 14

This is known to happen if you modified any of the default reports
I've seen that happening even in my lab (and and customers) where I am sure that I did not modify them. Just delete them (they should be prefixed with "_").
Torsten Meringer | http://www.mssccmfaq.de

Upgrade to SCCM 2012 R2 Failed - Can I Simply Move SCCM Database to Replacement SCCM 2012 R2 System?

I started with SCCM 2012 RTM and attempted an upgrade to SCCM 2012 R2. The upgrade failed and left the the system unusable. I was able to recover the entire system (single server) from backup.
Rather than risk another failed upgrade can I simply build a new server and move the existing SCCM database to a new SCCM 2012 R2 system?

Hi,
Here is an official article talks about Upgrade for your reference.
Planning to Upgrade System Center 2012 Configuration Manager
http://technet.microsoft.com/en-us/library/jj822981.aspx
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.

SCEP going out to the internet after being migrated to SCCM 2012 and saturating facility MPLS.

I was unaware of the fact that SCEP was gonig out to the internet to pull down 120 megs worth of data each time a client is migrated. I'm trying to determine the easiest or best way to avoid this. I've done some research and it looks like bundeling the SCEP
policy with the migration package might work. I also saw some tool that you can use to add a SCEP update rollup to the package. Ultimately if i could just get the exact URL the clients are going out to our networking team could apply QoS to this URL. Unfortunately
though it appears in the MPCMDRUN.log to go to go.microsoft.com/fwlink, but on the networking side in pathview i seen the client ends up going to Akamai.
I'm assuming MS offloads their web traffic to Akamai and that first link is redirected, if that is even the right link. Does anyone know a way i can prevent this while still getting the client up to date. This entire time I thought the clients would pull
what they needed from the SCCM 2012 env. I'm using ADR to push the definitions and that seems to be working fine except for 2 situations. One a client is migrated, or 2 the client comes online after being offline for more than 7 days and goes out.
Either way if someone could provide me with the URL for throttling or a better method for deploying I would be very grateful. So far we've migrated about 8 thousand clients and have about another 10 thousand to go. The majority of the clients have local
pull DPs, and if further details of my infrastructure would be helpful please just let me know.
Thanks,
-KR

Jorgen,
I appreciate you pointing out the setting and that has helped partially and I was able to track down the URL that is being used by the clients for QoS by networking. Now management has pushed back with why are the clients going to the internet at all. I
can understand why. If were deploying all the patches why can't the clients pull their SCEP engine from the SUP/WSUS server. I see it finding it in the MPCMDRUN.Log file but it still goes out to Microsoft to pull the 120 meg file. Do i not have any other options
for pushing the engine to the clients, if ADR is working for current clients what am i missing. I'm sure its something obvious, but my migration is on hold up until I can keep the clients from going to the internet for their new engine and deltas.
Any help you could provide i would very much appreciate. Thanks again Jorgen.
-Sam Kachar

IBCM Migrating existing SCCM 2012 Clients

Hi, We have in our current environment 120,000 endpoints configured on CAS with 3 Primary sites. All the clients are currently setup for SCCM 2012.
We started new project to introduce IBCM in the environment and here is the question on the clients, what is needed to setup the existing clients for IBCM, so basically when connected on the "Intranet" they will use infrastructure on the Intranet
and when connected to the "Internet" they would use our infrastructure we installed in the DMZ with Public DNS entries etc....
what I like to understand is what is needed on the existing clients to configure them to be IBCM aware.
I've done some testing in my Dev environment and managed to configure client using https and PKI Certs.
Few questions on this
New Client Installation parameters
currently we have installed all our clients using following command line "/Service SMSSITECODE=AUTO" I've left out the other parameters but basically the current clients are not IBCM aware
New install command I'm using: /Service /UsePKICert SMSSITECODE=<SiteCode> CCMHOSTNAME=<FQDN MP>. With this command line the client gets installed on the Intranet I can see it does recognize the Certificate, however when I switch
over to the internet, checking control panel applet it's still saying "Client Certificate: Self-signed" ==> Would this not switch to PKI? to be clear for my Intranet I don't use https but just http and I would like to keep it that way.
I've tried using the script I found on TechNet and that does set the Internet MP, but checking the properties of the client it still shows "Client Certificate: Self-signed", even when connected on the Internet.
Client Migration
I've tried using the script I found on TechNet and that does set the Internet MP, but checking the properties of the client it still shows "Client Certificate: Self-signed", even when connected on the Internet.
Does it require to re-install the client so it will be IBCM aware? We're planning to upgrade our Client to R2 release in August, would it be sufficient if I then update the ClientPush parameters to include the IBCM specific parameters and guess
that would work also?
Thx.

Hi Jason, thx for the reply and here are some answers to your questions early
Background is R2, but clients are not yet upgraded (SCCM 2012 SP1), they will be upgraded aug-sept time frame, using the built-in upgrade process, obviously after doing our testing :-)
You said:
"No, you should not have to do anything for the clients to be Intranet and Internet capable as long as they have properly trusted and valid client auth certs. Note that this includes being able to reach the CRL on an accessible CDP."
==> How is the client then going to find his Internet Management Point? I know the clients gets MP List every 25 hours I assume that would include the Internet MP's, is that the way the client will find the internet mp?
Checking the logs on 1 client I can see in "ClientLocation.log"
               Client is internet
               Current internet Management point is <empty>
if I check the control panel applet - "Network", the Internet MP is empty for that particular client.
I will have full infrastructure available in DMZ, currently doing my testing in DEV environment, have to be creative in faking Intranet/Internet using 2 separate networks
Follow-up question.
If I understand you correctly, I don't have to change anything on the installation params that I'm currently using. This assumes clients have valid certificates and can access CRL.
thx again for your help appreciated.

SCCM 2007 Migration to SCCM 2012

Hello,
I read http://social.technet.microsoft.com/Forums/en-US/58ba35e5-d84e-4741-8089-624f5269a2ca/sccm-2012-design-consideration-advice?forum=configmanagergeneral&prof=required with the following notes:
Secondary vs. DP is a subjective call based on two factors: client count and available bandwidth. More clients and/or less bandwidths means secondary site, less clients and/or more bandwidth means DP. Both use a server OS so there's really no cost difference, just some added complexity for a secondary site. Without knowing the bandwidth, no way for me to be able to say one way or the other.
As for IBCM, correct, it's no a primary site server, it's simply a site system that typically hosts an MP, DP, and SUP. The App Catalog Website Point is also applicable.
Are you planning on managing legacy mobile devices or Mac OSX? If not, the Enrollment Proxy Point is not needed -- it's not applicable to IBCM anyway to my knowledge.
Also, the FSP must be on a separate site system so that clients can communicate with it via HTTP.
I have for now two sites:
- 25,000 Desktops on one site
- 1,500 Servers on the second site
in SCCM 2007 I had three sites: One Parent doing the reporting and two child sites handling the inventory, distribution, etc... (No SUP do far)
I have on each child sites 1 DP.
What should be changed for SCCM 2012?
What is "More Clients" or "Less Clients" ?
"More Bandwidth" or "Less Bandwidth"?
Thanks,
Dom
System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hello Dom,
If you have Two Primary servers you may need to plan for a CAS (Central administration site), in SCCM 2012 when you have more than one primary server you need a CAS to connect them. But remember the CAS does not
process any client data, DPs nor MPs (hardware nor software inventory), and bear in mind that a primary stand-alone can support up to 100,000 clients, and in SCCM 2012 the big idea is to simplify the hierarchy. So if you have a primary site you can manage
a lot of clients, and you can separate them in your case in boundaries, boundaries in 2012 do two things: Site assignment and content lookup, but they only work with boundary groups, in which you set the limits in the boundary, and latter associate it with
a boundary group.
You can then just have a primary server and remote DPs, and decide how the clients will look for content in the DPs with the boundaries and boundary groups. The bandwidth needs to be really important about sending
packages between sites, or if the boundaries are not configured properly the clients can end up looking for content where it should not. Also don’t forget about fallback packages and content, because DPs and packages can be set as fallback, so if clients
cannot find in a local DP they will search those packages.
Below a few references that may help you with your migration.
Any more questions, please let me know.
References
==========
Planning for Configuration Manager Sites and Hierarchy
http://technet.microsoft.com/en-us/library/gg682075.aspx
Planning for Sites and Hierarchies in Configuration Manager
http://technet.microsoft.com/en-us/library/gg712681.aspx
Migrating Hierarchies in System Center 2012 Configuration Manager
http://technet.microsoft.com/en-us/library/gg682006.aspx
VIDEOS
========
Configuration Manager 2012: Plan, Deploy, and Migrate from Configuration Manager 2007
http://technet.microsoft.com/en-us/video/configuration-manager-2012-plan-deploy-and-migrate-from-configuration-manager-2007.aspx
Microsoft System Center Configuration Manager 2012: Plan, Deploy, and Migrate from Configuration Manager 2007 to 2012
http://channel9.msdn.com/Events/TechEd/Europe/2012/MGT313
Cheers,
Renato S. Pacheco

After migration from sccm 2007, there are many systems with no client installed

Hi Everyone,
We have migrated our environment from SCCM 2007 to SCCM 2012 , And Manual client push installation has been done by HeadQuarter SCCM admins on site code of our region.
But as i see , in all systems collection based on OU, there are approx 50% systems with no client installed.
There may be some stale systems in AD.
Is there any way so that i can list out all Stale or old computers which are not in use anymore records of systems from Active directory and so that i move them to OU for which system discovery is not enabled.
Also, it will very useful if i get more information on lastLogonTimeStamp and such more properties which specifies system as stale or OFF the network for some period..

You could also remove the objects without a client and adjust the settings in the
Options tab of the Active Directory System Discovery Properties. By tweaking those options you can make sure that you're not discovering those old objects in the first place.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SCCM 2007 migrated clients (SCCM 2012) are still visible

Hi,
We migrated some SCCM 2007 Windows 7 clients to SCCM 2012 (upgraded the clients via push).
This worked fine for most of the clients but not all so I cannot just delete clients from SCCM 2007.
How can we clean the succesfully migrated? I cannot see which ones are succesfully migrated in SCCM 2007, the all show active (even the succesfully migrated ones).
Pls advise.
J.
Jan Hoedt

The client will become inactive if it's not requesting client policies, sending heartbeats, sending inventories, or sending status messages any more in a period of by default 7 days (but it all depends on the configured intervals). Also, if you
delete clients that are still active, they will come back with the next heartbeat if they are still active.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Random BSOD after installing port replicator drivers.

Hi, my boss just got a new laptop (TP T400s running Windows 7) and after configuring it, it was working fine. But then I installed the drivers for the USB port replicator with digital video and after rebooting, right after the login screen, it BSOD, complaining about igdkmd64.sys. Rebooted again, it didn't crashed upon login this time, just a little while later when clicking on the start menu. After more test, the replicator seemed to work, but not the digital video port. The DVI connector didn't worked correctly, just the mouse pointer was being displayed. Trying to set resolution didn't do anything and switching output source via Win-P provoked a strange flickering for a minute or so and then the machine automatically rebooted. Tried the driver found on the CD (1.0) and also those available through Lenovo website (1.5.6.8), always the same thing. Now I've uninstalled the drivers and the random BSOD keep reappearing.
Is this issue common? Is the port replicator faulty or is it the ThinkPad? Is the windows installation screwed, can it be repaired? What is Lenovo return policy?
I've also seen lots of complaints on this forum about random shutdown, this would be as unacceptable for us than the current BSOD we're experiencing. Is that situation widespread?
P.S.: We're trying to get work done, not beta test Lenovo products!
Thanks
Solved!
Go to Solution.

nbuduroi wrote:
Hi, my boss just got a new laptop (TP T400s running Windows 7) and after configuring it, it was working fine. But then I installed the drivers for the USB port replicator with digital video and after rebooting, right after the login screen, it BSOD, complaining about igdkmd64.sys. Rebooted again, it didn't crashed upon login this time, just a little while later when clicking on the start menu. After more test, the replicator seemed to work, but not the digital video port. The DVI connector didn't worked correctly, just the mouse pointer was being displayed. Trying to set resolution didn't do anything and switching output source via Win-P provoked a strange flickering for a minute or so and then the machine automatically rebooted. Tried the driver found on the CD (1.0) and also those available through Lenovo website (1.5.6.8), always the same thing. Now I've uninstalled the drivers and the random BSOD keep reappearing.
Is this issue common? Is the port replicator faulty or is it the ThinkPad? Is the windows installation screwed, can it be repaired? What is Lenovo return policy?
I've also seen lots of complaints on this forum about random shutdown, this would be as unacceptable for us than the current BSOD we're experiencing. Is that situation widespread?
P.S.: We're trying to get work done, not beta test Lenovo products!
Thanks
The win7 driver for the usb port replicator with digital output is not out yet. So, you cannot get it work under win7. I recall seeing an official flyer of the product, in which there is a line stating that a win7 driver will be out in December.

Cross Forset Migration from sccm 2012 to sccm 2012RS

Hi all,<o:p></o:p>
We have a plan to migrate
sccm 2012 to sccm 2012 R2 on trusted forest (cross forest migration)<o:p></o:p>
Please share possibility...<o:p></o:p>
Thanks, Mariappan Shanmugavel

Possibility for what?
Migration only works from ConfigMgr 2007 SP2 or from the same version of ConfigMgr 2012 thus will not be able to migrate from 2012 to 2012 R2. You will need to upgrade your 2012 site to 2012 R2 first and then perform the migration. The TechNet docs clearly
show this: http://technet.microsoft.com/en-us/library/gg699364.aspx
ANd, as Torsten pointed out, if you are simply planning on moving the existing site server, that isn't supported and won't work either.
Jason | http://blog.configmgrftw.com | @jasonsandys

Random BSOD after migrated to SCCM 2012 R2 - System Endpoint Protection

Similar Messages

Maybe you are looking for