iontoria

Does anyone have any contribution about this? Thanks!

Hello: I have one problem with the SMPs in my architecture. We have two distribution point with state migration point role installed. The folder that stores the USMT data is called for example SMPSTOREF_B5517EAC$ and every time I restart the server the permissions assigned to that folder or parent folder are missed. We need to add some specific users with read-only permissions and it dessapeared when the server is restarted. I have tested to assign permissions to the parent folder or to the drive and apply inheritance, but it doesn´t works. Could someone explain me how permissions work in this special folder and how to apply inheritance to it? Thanks a lot in advance.

Hello: I have a lab where we are making a migration process from SMS and WSUS to SCCM 2012. I have a problema with WSUS migration. In the SCCM 2012 primary site I have installed and configured WSUS and SUP role. I made the followind proc: export the wsus metadata in the actual wsus server, move the WsusContent directory and then import the wsus metadata in the WSUS server in the lab. After these steps I´m able to view the updates trought the WSUS console in the SCCM 2012 server, but I can´t see these information in the SCCM console. As we are in a lab environment we don´t have internet connection, so we can´t connect to Windows Update. Which is the way to see the updates i have in the SCCM 2012 console? Any help would be appreciated. Ivan

Hello: I´m trying to make a implementation of WSUS/SUP in my SCCM 2012 lab. I have 1 CAS and 2 primary sites (one for servers and one for intranet clients). I have to implement WSUS and I´m planning to put it under NLB. So I have deploy 2 Windows 2008 Servers, joined them to the domaind and I have installed WSUS 3.0 SP2. I have installed and configured NLB with these two machines. After that, from the primary site Configuration Manager 2012 console I have added one new site system server with the MP and SUP roles. In the Primary Site-->Site Configuration-->Sites i have configured the Software Update Point component with these settings: - Use Network Load Balancing cluster for active siftware update point - Put th NLB IP adress and the ports (8530 and 8531 in my case because I have a custom web site for WSUS). - An account with privileges. I have several doubts about this schema: 1) firstable, is the rigth way to make this type of implementation? 2) In the primary site there´s no WSUS installed, only SUP role. Is this correct? Do I have to install WSUS 3.0 SP2? Full installation or only administration console? 3) The CAS server is the only active software update point. It´s OK? Any help about this would be appreciated. thanks in advance. Ivan

Hi again! We have resolved the problema. It was an issue with DNS entries. The gather information process has worked finally! Thanks!

Hi again: looking at migmctrl.log at CAS server (I had notice yesterday that this is the server that really process the migration instead of the Primary site Server from which I launch the migration) I found two errors. This is te complete trace: [MigMCtrl]: NOTIFY job manager ( 1, 0, C:\Program Files\Microsoft Configuration Manager\inboxes\mmctrl.box\16777223.SYN ). SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) Connection string = Data Source=(local);Initial Catalog=CM_CAS;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Encrypt=True;TrustServerCertificate=False;Application Name="Migration Manager". SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) Created new sqlConnection to (local) SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: Start processing schedule changed event for MIG_SiteMapping.ID=16777223 SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: Can not find schedule item with ID 16777223 and type MIG_SiteMapping. SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: The schedule item with ID 16777223 and type MIG_SiteMapping is either deleted or processed at CAS site. SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: End processing schedule changed event for MIG_SiteMapping.ID=16777223 SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigMCtrl]: EVENT raised ( 1, 0, C:\Program Files\Microsoft Configuration Manager\inboxes\mmctrl.box\16777223.SYN ). SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigMCtrl]: NOTIFY job manager ( 1, 0, C:\Program Files\Microsoft Configuration Manager\inboxes\mmctrl.box\16777224.SYN ). SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) Connection string = Data Source=(local);Initial Catalog=CM_CAS;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Encrypt=True;TrustServerCertificate=False;Application Name="Migration Manager". SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) Created new sqlConnection to (local) SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: Start processing schedule changed event for MIG_SiteMapping.ID=16777224 SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: Update the DateNextRun of the schedule item MIG_SiteMapping.ID=16777224 SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: Calculating the next run time ... SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: This is a recurring schedule token. SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: This item hasn't run yet, we will run it immediately. SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: Check requested operation for schedule item MIG_SiteMapping.ID=16777224 SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: Start operation requested, the scheduled item 16777224 will be started once computing resource is allocated. SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: End processing schedule changed event for MIG_SiteMapping.ID=16777224 SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigMCtrl]: EVENT raised ( 1, 0, C:\Program Files\Microsoft Configuration Manager\inboxes\mmctrl.box\16777224.SYN ). SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigMCtrl]: 2 instruction file processed. SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) Connection string = Data Source=(local);Initial Catalog=CM_CAS;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Encrypt=True;TrustServerCertificate=False;Application Name="Migration Manager". SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) Created new sqlConnection to (local) SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: Start two step scheduling for MIG_SiteMapping SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: Step 1. Query the schedule items that was running or requested to start immediately ... SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: Clear the requested operation. SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: Calculating the next run time ... SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: This is a recurring schedule token. SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: This item already run at 02/29/2012 07:07:38 UTC, 02/29/2012 08:07:38 Local Time, the next run time is 02/29/2012 11:07:38 UTC, 02/29/2012 12:07:38 Local Time. SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: Set the next run time to 02/29/2012 11:07:38 UTC, 02/29/2012 12:07:38 LocalTime. SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: Got an scheduled item 16777224. Set the sleep time to 0. SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: End two step scheduling for MIG_SiteMapping SMS_MIGRATION_MANAGER 29/02/2012 8:07:38 2900 (0x0B54) [MigrationManager]: Impersonation is about to start ... SMS_MIGRATION_MANAGER 29/02/2012 8:08:10 2900 (0x0B54) [MigrationManager]: Impersonation succeed, current user identity is: EJGVNET\IONTORIA SMS_MIGRATION_MANAGER 29/02/2012 8:08:10 2900 (0x0B54) Connection string = Data Source=EJWP115;Initial Catalog=SMS_EJZ;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Encrypt=True;TrustServerCertificate=True;Application Name="Migration Manager". SMS_MIGRATION_MANAGER 29/02/2012 8:08:10 2900 (0x0B54) [MigrationManager]: Impersonation is reverted. SMS_MIGRATION_MANAGER 29/02/2012 8:08:26 2900 (0x0B54) STATMSG: ID=8610 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_MIGRATION_MANAGER" SYS=SCCM2012SCSQL.ejsarea.net SITE=CAS PID=2024 TID=2900 GMTDATE=mié feb 29 07:08:26.681 2012 ISTR0="SCCM2012SCSQL.ejsarea.net (CAS)" ISTR1="ejwp115.ejsarea.net" ISTR2="-2146232060" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_MIGRATION_MANAGER 29/02/2012 8:08:26 2900 (0x0B54) [MigrationManager]: Set the schedule item 16777224 to Failed. SMS_MIGRATION_MANAGER 29/02/2012 8:08:26 2900 (0x0B54) ERROR: [MigrationManager]: Error occurred when trying to make sql connection to EJWP115. Contact product support for help. Error Information -2146232060, Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. SMS_MIGRATION_MANAGER 29/02/2012 8:08:26 2900 (0x0B54) ERROR: [MigrationManager]: Microsoft.ConfigurationManagement.Migration.MigrationException: Error occurred when trying to make sql connection to EJWP115. Contact product support for help. Error Information -2146232060, Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error) at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket() at System.Data.SqlClient.TdsParser.ConsumePreLoginHandshake(Boolean encrypt, Boolean trustServerCert, Boolean& marsCapable) at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at Microsoft.ConfigurationManager.ManagedBase.SqlConnectionBuilder.GetSqlConnection(String sqlServerName, String sqlInstanceAndDatabaseName, String applicationName, SqlConnectionSecurityLevel securityLevel) at Microsoft.ConfigurationManagement.MigrationManager.ConnectionBuilder.BuildSqlConnection(Dictionary`2 context) --- End of inner exception stack trace --- at Microsoft.ConfigurationManagement.MigrationManager.ConnectionBuilder.BuildSqlConnection(Dictionary`2 context) at Microsoft.ConfigurationManagement.MigrationManager.JobManagerBase`1.<get_ConnectionFactory>b__0(Dictionary`2 n) at Microsoft.ConfigurationManagement.MigrationManager.ObjectFactory.<>c__DisplayClass1`1.<Register>b__0(Dictionary`2 n) at Microsoft.ConfigurationManagement.MigrationManager.ObjectFactory.TryCreate[T](Dictionary`2 context) at Microsoft.ConfigurationManagement.MigrationManager.JobManagerBase`1.ConnectToLegacySite(IMigrationSiteInfo siteInfo) at Microsoft.ConfigurationManagement.MigrationManager.SyncAgentJobManager.CreateJob(MigrationRepository repository, MIG_SiteMapping scheduleItem) at Microsoft.ConfigurationManagement.MigrationManager.JobManagerBase`1.GetNextJob(Int32& sleepMilliseconds) SMS_MIGRATION_MANAGER 29/02/2012 8:08:26 2900 (0x0B54) [MigrationManager]: Start two step scheduling for MIG_SiteMapping SMS_MIGRATION_MANAGER 29/02/2012 8:08:26 2900 (0x0B54) [MigrationManager]: Step 1. Query the schedule items that was running or requested to start immediately ... SMS_MIGRATION_MANAGER 29/02/2012 8:08:26 2900 (0x0B54) [MigrationManager]: Step 2. Query the first item in order of DateNextRun ... SMS_MIGRATION_MANAGER 29/02/2012 8:08:26 2900 (0x0B54) [MigrationManager]: The item MIG_SiteMapping 16777224 is scheduled to run at 02/29/2012 11:07:38 UTC, 02/29/2012 12:07:38 Local Time, sleep for 03:59:11.8270000. SMS_MIGRATION_MANAGER 29/02/2012 8:08:26 2900 (0x0B54) [MigrationManager]: End two step scheduling for MIG_SiteMapping SMS_MIGRATION_MANAGER 29/02/2012 8:08:26 2900 (0x0B54) Connection string = Data Source=(local);Initial Catalog=CM_CAS;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Encrypt=True;TrustServerCertificate=False;Application Name="Migration Manager". SMS_MIGRATION_MANAGER 29/02/2012 8:08:26 2900 (0x0B54) Created new sqlConnection to (local) SMS_MIGRATION_MANAGER 29/02/2012 8:08:26 2900 (0x0B54) [MigrationManager]: Start two step scheduling for MIG_Job SMS_MIGRATION_MANAGER 29/02/2012 8:08:26 2900 (0x0B54) [MigrationManager]: Step 1. Query the schedule items that was running or requested to start immediately ... SMS_MIGRATION_MANAGER 29/02/2012 8:08:26 2900 (0x0B54) [MigrationManager]: Step 2. Query the first item in order of DateNextRun ... SMS_MIGRATION_MANAGER 29/02/2012 8:08:26 2900 (0x0B54) [MigrationManager]: No item found. Sleep until the next event. SMS_MIGRATION_MANAGER 29/02/2012 8:08:26 2900 (0x0B54) [MigrationManager]: End two step scheduling for MIG_Job SMS_MIGRATION_MANAGER 29/02/2012 8:08:26 2900 (0x0B54) [MigMCtrl]: the workitem queue is full! SMS_MIGRATION_MANAGER 29/02/2012 8:08:26 2900 (0x0B54) [MigMCtrl]: WAIT 3 event(s) for 60 minute(s) and 0 second(s). SMS_MIGRATION_MANAGER 29/02/2012 8:08:26 2900 (0x0B54) The error says something about a timeout period expires. I have test the connection from the CAS server to the SCCM 2007 server and is OK and this error appears after 1 minuto more or less (so it cannot be a timeout error). Could anyone give any ideas? Thanks a lot!

Hi: I´m trying to make a migration from SCCM 2007 to SCCM 2012. I have installed a CAS and a Pimary Site (which is going to host the content of the SCCM 2007 server) in a SCCM 2012 hierarchy. Then, I start the migration wizard from the Primary site created before and configure the accounts. I´m using my personal account, which is domain admin and administrador in both machines. Is a sysadmin account inside SQL Server and is member os the SMS Admin group in SCCM 2007. In SCCM 2007 the version of SQL Server is 2005. The ports 1434, 135 and 445 are open between the servers. The error message i´m getting is: "Configuration Manager failed to gather data from <server>" Configuration Manager failed to connect the databse of the source site. Ensure the source site database server is online, that the specified credentials have Read and Execute permissions to the source site database, and that firewall exceptions are configured and include the following ports: 1433 (TCP) , 1434 (TCP) " There´s no firewall between the server (they are in a virtual server) and all ports are open. Why the message says anything about 1434 port? I think this is an UDP port, and we only need is 1433. I test the connection from the migration wizard and it´s OK. Any ideas would be appreciated. Thanks a lot in advance!

Hi, again: maybe with wsusutil export filename.cab logfile.xml and wsusutil import filename.cab logfile.xml?

Hello: We´ve a WSUS and SMS 2003 infraestructure and now we are planning the migration to SCCM 2012. In WSUS case, we have defined our sttings (groups, types of updates to download, classifications...). Is there any way to translate this information to SCCM 2012? Maybe trougth export/import jobs? Programmatically? Thanks in advance.

Hi, anyweb: I understand what you say. SCCM 2012 have tools that can help us in the migration process because they gather the information from SCCM 2007 and import it in SCCM 2012, rigth? So the problem is that there´s no way (scripts, third party tools...) to export the information stored in SMS 2003 and import it in SCCM 2012, is it? thanks a lot again.

Hello: firstable thanks for these series of posts! they are a great value. I have a doubt about the migration to SCCM 2012. We have a SMS 2003 infraestructure and we are planning to migration to SSCM. The first option was SCCM 2007 but because SCCM 2012 is in RC version we are thinking to migrate to this latest product version. Reading this post yo mention this: "You cannot upgrade from SMS 2003 to Configuration Manager 2012, the only supported method is to migrate from SMS 2003 to Configuration Manager 2007 (in-place or side-by-side) and then perform a side-by-side migration to Configuration Manager 2012. Or, you could call it a day on SMS 2003 and start fresh with Configuration Manager 2012." Could you explain a little more this? Why is not possible to migrate from SMS 2003 to SCCM 2012 (side by side)? Thanks a lot again.