Jump to content


Search the Community

Showing results for tags 'Migration'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests

  1. Hey Guys / Niall - So I manage an environment of ~10,000 workstations and ~900 servers on a single domain. A few months ago, we acquired a new company which has their own SCCM environment on a different domain. Finally, I am wrapping up a build of SCCM on a 3rd domain. The plan is to migrate all clients from the two old domains onto the new one. I have a couple of questions about this procedure so wanted to post to get opinions... 1. Migrate Many Clients to New Site Prior to Domain Change The main question is that their current plan is to migrate the domain on workstations a department at a time over a six month period. While doing so, they want to use my script to migrate each of the workstations' SCCM client while changing the domain. The last thing i want is to have 3 separate and constantly changing environments to manage, so am trying to find the best way to potentially migrate the clients from both old domains to the new one before (like few months in some cases) the domains on the workstations are changed. There's currently a one-way trust between the new domain and both old ones and don't know if I can get them to make it more flexible. Basically, I'm curious what I would need to do in order to achieve the goal above. My experience tells me the below would be needed - at least in theory: Add scope of system's OUs / containers in old domain to discovery on new site Script executed per system to change the site of the client to the new site The SCCM Network Service account to have local admin rights on all workstations (per old domain) Specific DNS records modified / changed to point to the FQDN of the new primary instead of the old ones (per old domain) Is the above all that would be required, know of any helpful posts related to this, or any suggestions / thoughts? 2. Migration of Packages, Applications, etc with New Source Path I'll be moving a lot of packages and such over to the new environment, but am now using a new "master" share for the sources of all packages, applications, etc. It's simple to migrate an SCCM package from one site to a new one, but when doing so; it retains the same source path for it. Does anyone know of a PowerShell script or overlooked options which would allow me to change just the first part of the source path for migrated packages when moving to the new site? If capable of copying the source content during the migration, that would be ideal; but if not copying it would still be faster than changing each manually. I'm considering simply exporting certain packages, then importing them back in. Will have to play with that a bit more to see how it would work. Suggestions? All 3 sites run SCCM 2012 R2 SP1 CU4. We cannot go to current branch yet due to numerous legacy apps on workstations which don't play nice with .NET 4+. Most site servers (especially on the new environment) run Windows 2012 R2. Any suggestions or comments would be appreciated. Thanks!!
  2. I will give background about the scenario, we are in the process of Side-by-Side Migration from SCCM 2012 R2 to SCCM 1906 CB. As per the guideline, I have configured the products classification in the new site identical like the old site and synchronized. Now I am at the phase of the migrating Applications, Collections, ADR, Software Update Package and its deployment. For E.g.: I am trying to migrate Office 2010 Software Update Package and its deployment and it’s all associated collection and rules from SCCM 2012 R2 site to SCCM 1906 Site. Migration is failing and the error was that the destination site doesn’t have software updates with unique id: b2f2052b-d652-4895-bc2e-c5105acadb00, 10756e43-6c49-45c1-a897-12b4e89fdc11 Screenshot for your reference below as i couldnt paste it here I have given below a details screenshot of the error from the Migration manager log: The migration manager is complaining that file lib id b2f2052b-d652-4895-bc2e-c5105acadb00 doesn’t exist in the destination hierarchy so it couldn’t move the Office 2010 package from SCCM 2012 to SCCM 1906. I was looking for this update in the all software update group list. I was even unable to find that software update even in the SCCM 2012 R2 Hierarchy, which means that content_id is invalid and stale. It needs to be removed from the package id so the migration manager won’t look into it during migration Below is the screenshot for location the where all the software update deployment package are: When I open this package id, I was able to find all the references of all software update in it: screenshot given below for your reference: If you look at the screenshot above, the Office software deployment package has the reference of a software member (b2f2052b-d652-4895-bc2e-c5105acadb00) in it, so the migration manager is looking for it the new site. However i have checked Microsoft Catalog to see if the above unique_id is what software update, but even it is not in Microsoft Catalog. I think it is a stale unique Id which needs to be removed from the package. Due to the reference still exist in the Package, the migration manager is not able to migrate the package from SCCM 2012 R2 to SCCM 1906 CB. PS: I have used content library clean-up tool but it freed up only the orphaned contents in the DP. But it didn't remove the stale references from the Package. Also I have validated the package and even redistributed the content again to the DP to see if it fixes the issue. I used t-sql query to find the article Id and title information from in the SQL db, but there is no information. can you guys help me to fix the issue. The main agenda is to migrate all contents from current hierarchy to the new hierarchy.
  3. Not sure how to even search for this, and trying to set up a computer association isn't doing anything (seriously seems to be limited strictly to user state data). And I need to be able to set this up for computer names that have yet to be created. Is there a way to quickly make computer objects with just a name and collection membership? When we deploy windows to the new machines, they all need different software installed and rely upon collection membership to provide the right packages. If this is not something that can be done, how do you all deal with a new batch of computers that people need to be moved to without installing all the software by hand? Thanks
  4. Cross Post from https://www.ccrossan.com/sccm/sccm-1511-driver-migration-fails/ While migrating drivers from SCCM 2012 to SCCM 1511, the migration can fail with the following error message: Couldn't find the specified instance SMS_CategoryInstance.CategoryInstance_UniqueID='DriverCategories: This occurs given the following scenario: A driver is added to SCCM A category is assigned to the driver The category is deleted from the driver The migration job attempts to migrate the driver to a new SCCM environment Consider the following error message: Couldn't find the specified instance SMS_CategoryInstance.CategoryInstance_UniqueID='DriverCategories:78266da1-ebac-4c12-b2c8-89451383b03e An In-depth analysis shows that the driver category does not appear in the WMI Class SMS_CategoryInstance: Get-WmiObject -Namespace $Namespace -Class SMS_CategoryInstance -Filter "CategoryInstance_UniqueID = 'DriverCategories:78266da1-ebac-4c12-b2c8-89451383b03e'" Returns Null, but a SQL query indicates that the Category Instance still exists: SELECT * FROM CI_CategoryInstances WHERE CategoryInstance_UniqueID LIKE ‘%78266da1-ebac-4c12-b2c8-89451383b03e%’ Returns the following: CategoryInstanceID CategoryInstance_UniqueID CategoryTypeName DateLastModified SourceSite ParentCategoryInstanceID IsDeleted rowversion 16777602 DriverCategories:78266da1-ebac-4c12-b2c8-89451383b03e DriverCategories 2015-07-27 11:52:33.000 CM1 NULL 1 0x000000000A36B34D Take note of the “IsDeleted” column – set to True So, at this point, WMI reports that this category no longer exists; however the category is still in the SQL Database, though this is not the root of the problem. Now consider the WMI Class SMS_CategoryInstanceMembership: This class contains a correlation of Objects to CategoryIDs. This is not limited to Driver <-> Driver Category correlation. The true bug seems to be that when a driver category is removed, the entry for that driver category in the SMS_CategoryInstanceMembership class is not removed. In order to fix this, and have a successful migration, we need to manually remove the CategoryInstanceMembership object for any drivers that were assigned a now deleted category. to Fix: Fire Up SQL Server Management Studio Create a New Query, and select your Site Database For each failing driver entry (as seen in “C:\Program Files\Microsoft Configuration Manager\Logs\migmctrl.log”), Run the following SQL Query: SELECT * FROM CI_CategoryInstances WHERE CategoryInstance_UniqueID LIKE '%c6e9d9e3-1371-46ba-b7f1-bb46c5b6bc06%' Note the CategoryInstanceID (should be like 16777601) On your SCCM Server, from an administrative PowerShell run the following code to remove the association, substituting the CategoryInstanceID you discovered in step 3-2: Get-WmiObject -Namespace $Namespace -Class SMS_CategoryInstanceMembership -Filter "CategoryInstanceID = '16777601'" | Foreach-Object { Remove-WmiObject -InputObject $_ } Repeat the above section for each unique CategoryInstance_UniqueID listed in the “C:\Program Files\Microsoft Configuration Manager\Logs\migmctrl.log” file. When complete, retry the migration, and examine for any additional missing CategoryInstance_UniqueID errors.
  5. Hi, I`m buildiong my refresh task sequence to migrate from WIn7 to Win10, my Online USMT transfers the data, however the printer queue, Wallpaper and Outlook signature don`t get transferred, i`m using the default USMT settings. am I missing something? SCCM 1706 + ADK1703
  6. Hi All, Just looking for some advice, has anyone migrated their primary server from one machine to another? Looking at doing this, but wondering if there's any pitfalls I need to look out for. Thanks
  7. I am preparing to migrate from an over specced 2012 R2 hierarchy to a Stand alone primary running 1602 and wanted to get some opinions\feedback from the community before I finalized anything. I am undecided on whether or not to install sql on its own server or just install it on the site server. I know best practices used to be to install sql and config manager on the same server but wasn't sure if that was still the case.
  8. Hello everyone, I was wondering if anyone has experience in the field in migrating SCOM 2007 to SCOM 2012 R2. I understand there are effectively 2 methodologies: in-place or standalone upgrade. But apart from exporting/importing Management Packs, what other areas need be to looked at? How can you tell if an MP is using unsupported features in 2012? Looking forward to hearing any experiences you can provide. Thank you :-)
  9. Published: 2013-06-06 (at www.testlabs.se/blog) Updated: - Version: 1.0 This post will focus on having the technical prerequisites ready and in place for a successful Domino/Notes migration. Before going into any details, if you are planning to do a migration from Domino and want to use Dell Software’s Notes Migrator for Exchange, it is important to mention that there is a requirement from the vendor to use certified people for the project. If you would like to read the other parts: Part 1: Migrations – Overview Migration Accounts I recommend using three accounts, one with Domino permissions, one with Active Directory (AD) permissions and one with Exchange permissions. Domino The Domino account should be Manager for all .NSF files (database files), Editor on the NAB (names.nsf) and Reader on all users archive files. Username example: Quest Migrator/DominoDomain This is done by following the steps below: Create a new migration account in People & Groups, select the directory and People. On the right hand side, press People – Register. Fill in a proper name, I typically create an account called Quest Migrator as shown in the example below. Finally, press Register. To configure the permissions on the NAB (directory), go to Files and select the directory (names.nsf), right click, choose Access Control and Manage. Add the account by browsing for it, give it the User type: Person and the Access: Editor. (see picture below) The final step is granting the Quest Migrator/dominodomain account Manager permissions on all NSF files that will be migrated. Go to Files and select the folder where the NSF files are located. Right click and choose Access Control and Manage. Add the account by browsing for it, give it the User type: Person and the Access: Manager. (see picture below) Active Directory For the AD account, it’s recommended to be a member of “Domain Admins”. However, this is not a requirement, because delegated permissions can be used. The important aspect is that the AD account have “Full Control” over the OUs where user objects are located. The AD account also needs to be a member of “View-Only Organization Management”. If using the provision feature within Notes Migrator for Exchange (NME), the AD account needs to have “Full Control” over the OU where the contact objects are located as well. This account also needs to have Remote PowerShell enabled, use the command: “Set-User ”SA-NME” –RemotePowerShellEnabled $True” Username example: Domain\SA-NME Migration User This user is not used for logging on interactively. The important aspect with this user is that it has the correct permissions on the Mailbox Databases. Configure the databases so that the account has Receive-As permissions, this can be done by using the command below: ”Get-Mailboxdatabase | Add-Adpermission -user “SA-MIG” -extendedrights Receive-As” Username example: Domain\SA-MIG Office 365 account Most permissions are done automatically by NME but you must manually set account impersonation. This is done by using the command below: New-ManagementRoleAssignment -Role "ApplicationImpersonation" –User SA-MIG More information about the migration performance and throttling can be found by reading the provided link in the end of this post. Throttling Policies and Windows Remote Management Another thing to keep in mind is the configuration of the Throttling Policies and the Windows Remote Management. If you are migrating to Exchange 2010, make sure to configure the Throttling Policy according to the configuration below. “New-ThrottlingPolicy Migration” “Set-throttlingpolicy Migration -RCAMaxConcurrency $null -RCAPercentTimeInAD $null ` -RCAPercentTimeInCAS $null -RCAPercentTimeInMailboxRPC $null” “Set-Mailbox “SA-MIG” -ThrottlingPolicy Migration” Also make sure to configure the Windows Remote Management with the following settings. “winrm set winrm/config/winrs '@{MaxShellsPerUser="150"}'” “winrm set winrm/config/winrs '@{MaxConcurrentUsers="100"}'” “winrm set winrm/config/winrs '@{MaxProcessesPerShell="150"}'” “winrm set winrm/config/winrs '@{AllowRemoteShellAccess="true"}'” “set-executionpolicy unrestricted” If you are migrating to Exchange 2013, the throttling policies have been changed. Create a new throttling policy and assign it to the migration mailbox “SA-MIG”. “New-ThrottlingPolicy Migration -RCAMaxConcurrency Unlimited -EWSMaxConcurrency Unlimited” ”Set-Mailbox “SA-MIG” -ThrottlingPolicy Migration” SQL Server Notes Migrator for Exchange leverages SQL for saving user information (and much more). The Native Client needs to be installed together with SQL Server 2005 or SQL Express 2005, or newer. I do prefer running at least SQL 2008 R2 and I would recommend using the SQL Server instead of the Express version, since you have more flexibility of creating maintenance jobs for example. A little heads up if you are about to run a large migration, make sure to take full backups of the NME40DB so that you have a copy of it, if anything happens and also for having the logs truncated. In smaller migration projects the SQL Express version works fine, I would still recommend taking full backup of the database or dumping it to a .bak file and then backup the .bak file. Configure the account “Domain\SA-NME” as DBCreator, for allowing it to create the NME40DB during the setup of Notes Migrator for Exchange. Lotus Notes client I would recommend you to use the latest Lotus Notes client. In my last projects I’ve been using version 8.5.3 Basic or Normal client. An important thing to never forget is to install Lotus Notes in single user mode. .NET Framework 4 Make sure to install the .NET Framework 4 since this is a prerequisite for NME. I would recommend upgrading it to the latest service pack level. Antivirus If Antivirus is installed, make sure all Quest folders and %temp% are excluded from any Antivirus scans. If not it may result in slower performance and potential disruption of migrated content. Most likely, there will be a mail gateway of some kind in the environment which takes care of the antispam. In those situations, antivirus and antispam are already addressed in the Domino environment. On the target side, Exchange probably has antivirus and antispam solution installed as a second layer protection to the Transport services. As a result, I have not encountered any problems when excluding a couple of folders for the migration from scanning process. Outlook Outlook 2007, 2010 and 2013 are all supported. I’ve been using Outlook 2010 in all my projects and it have been working very well. Configure Outlook with the “SA-MIG” account, since this is the account that will insert migrated content into the Exchange mailboxes using the Receive-As permission. I’ve been learned to create and configure a Outlook profile using the SA-MIG account. Make sure to configure it for not using the cached-mode. However, in theory, a profile should not need to be created in advance, because NME creates temporary profiles during the migration. However, this step shouldn’t hurt anything either. User Account Control (UAC) It’s recommended to disable UAC on all migration servers. This is done in the Control Panel under User Accounts, Change User Account Control settings. Make sure to set it to “Never notify” and then restart the sever. Data Execution Prevention (DEP) It’s highly recommended to disable DEP, so make sure to do that. If you’re using Windows 2008 R2 like I do, then you disable DEP by running: "bcdedit /set nx AlwaysOff" Also, make sure to restart the server when this is done to allow it to take effect. Local administrator If you choose to delegate the permissions instead of using the Domain Admin group for the SA-NME account, then it is required to add the SA-NME account into the local administrators group. Regional Settings During the migration, the folder names (Inbox, Inkorgen etc.) are created based on the regional settings on the migration console. So, for example, if you are migrating a UK/English mailbox, make sure to configure the regional settings to match this and for example, if migrating a Swedish mailbox, set it to match the Swedish locale settings. With this said, I would recommend migrating users using the same language at the same time. And then change the regional settings on the migration console and continue with another region. Office 365 Prerequisites Migrating to Office 365 is like a normal migration, besides the target is a cloud service which can be a bit special. There are two requirements that needs to be fulfilled on the migration servers before starting the migration to Office 365. Install the following (select the one that suits your operation system): MSOL Sign-in Assistant: 32 bit 64 bit MSOL Module for Windows PowerShell: 32 bit 64 bit The Admin Account Pooling Utility (AAPU) is used for getting better throughput performance. The AAPU tool provides a workaround by using different migration accounts for each migration thread, instead of having one migration account with a throttling limit, you could have ten migration accounts which would give 10 migration threads in total. You can have up to 10000 migration accounts (NME 4.7.0.82). If you are going to use the AAPU, you should add the parameter below into the NME Global Defaults or Task Parameters. [Exchange] O365UsageLocation=<xx> http://www.iso.org/iso/country_codes/iso_3166_code_lists/country_names_and_code_elements.htm For NME 4.7.0.82 the following text is stated in the release notes (always read them!): Office 365 Wave 15 Throttling: NME has been updated to better address the PowerShell Runspace throttling introduced in O365 Wave 15. In order to efficiently proceed with migrations to Wave 15, the tenant admin must submit a request through Microsoft to ease the PowerShell throttling restrictions. The tenant admin must open a service request with Microsoft and reference “Bemis Article: 2835021.” The Microsoft Product Group will need this information: tenant domain (tenant.onmicrosoft.com) version of Exchange (in this case, for Wave 15) number of mailboxes to be migrated number of concurrent admin accounts to be used for the migration number of concurrent threads to be used number of Runspaces to be created per minute* proposed limit (powershellMaxTenantRunspaces, powershellMaxConcurrency, etc.), and the number to which to increase the limit* * For the last two items in this list, the tenant admin should take the total number of threads across all migration machines and add a buffer, because it is difficult to predict the timing of the Runspace initiation. It is best to assume that all potential Runspaces could be created within a minute, so the values for both items should probably both be submitted as the total number. More information about migration performance and throttling can be found by reading the provided link at the end of this post. Network Ports Port In/Out Type Source Target Description 1352 Out Domino Quest NME servers All Domino mail serversDomino Qcalcon server Domino/Notes client (migration) 445 Out NetBIOS/SMB Quest NME servers All Domino mail serversDomino Qcalcon serverQuest NME master server Microsoft-DS/NetBIOS traffic for Migration. For reaching SMB shares. Note: Not required, but recommended. 389 Out LDAP Quest NME servers Active Directory DC server(s) LDAP 3268 Out LDAP GC Quest NME servers Active Directory DC server(s) LDAP Global Catalog 1025-65535 Out High-ports Quest NME servers Active Directory DC server(s)Exchange server(s) High-ports(differs depending on version) 1433 Out Microsoft SQL Quest NME servers Quest NME master server For reaching SQL DB 443 Out HTTPS Quest NME servers Office 365 Transferring migration content Notes from the field Network Monitoring or Wireshark may sometimes be your best friend during troubleshooting network connectivity. Portqry is another tool that could be of great value during initial network verification. Read through the release notes and the User Guide (PDF), it is included within the NME zip file. All information is collected into that document. Office 365 Migration Performance and throttling information Read the other parts Part 1: Migrations – Overview Part 3: Migrating Domino/Notes to Exchange 2013 On-premise Part 4: Migrating Domino/Notes to Office 365 Part 5: Migrating Resources Mailboxes, Mail-In databases and Groups Part 6: Prerequisites for Coexistence between Domino and Exchange 2013/Office 365 Part 7: Configuring Coexistence Manager for Notes with Exchange 2013 On-premise Part 8: Configuring Coexistence Manager for Notes with Office 365 Part 9: Prerequisites for Quest Migration Manager Part 10: Migrating User Mailboxes from Exchange 2003 to Exchange 2013 using Migration Manager Part 11: Migrating User Mailboxes from Exchange On-premise to Office 365 Feel free to comment the post, I hope you liked the information. If you find something that might be incorrect/other experiences, leave a comment so it can be updated.
  10. I've been tasked with migrating a customer off of server 2008 R2 to Server 2012 R2. All FSMO roles have been transferred to the newly created Server 2012 R2 DC's and replication is taking place. Tomorrow, I would like to migrate dns off of the 2008 boxes. The scopes have replicated to the new dns servers, but how to I make sure the clients get pointed to the 2012 dns servers once I take the 2008 servers offline? I do have dns integrated into AD. I'm stuck at the "ensuring primary dns server" becomes my 2012 DC. Would the below powershell command set this across the domain? Set-dnsclientserveraddress –interfaceindex 15 –serveraddress (“xx.xx.xx.xx”,”xx.xx.xx.xx”) Any advice would be greatly appreciated. Thank to everyone!
  11. Cannot solve this. Windows 7 32bit Currently we have one drive in our computers partitioned in to 2. (C: & D:) New setup One drive one partition. (C: only) Right now users store there data on the D: like documents and PST's. And some machines have the pagefile.sys Right now its easy I tell it to migrate the whole drive and I exclude some folders with an unconditional exlude. Works great. Even doesnt get the pagefile.sys on the D: If I run the loadstate on the machine now with just the one drive it dumps everything that was on the D: to the C:. Very messy plus the PSTs are now not connected. So I tried a realitive move comand to try and get it under the users profile in my custom.xml when I run scanstate. Now if the pagefile is on the D: and I add the relative move of the D: it fails saying it cant copy the Pagefile.sys. However I dont want it to and have specifically exclueded it. Any ideas to move the D: to a folder on the C: (doesnt really matter where) and make it work like it was when the D: was there?
  12. Hello, Looking for a bit of advice for anyone able to help. Implementing SCCM 2012 into a new organisation at the same time as a global refresh to a new domain. I need to capture user profiles from the old domain using USMT and restore to the new one. Is this possible? Thanks
  13. Hey guys looking for a bit of info here... We have an existing hierarchy of 1 CAS and 3 Primary sites, along with 13 secondary sites attached to 1 of the Primary Sites. I just learned that during the setup of these sites SQL 2012 Enterprise Evaluation Edition was used to install all the sites. Now the Evaluation Edition on the CAS SQL server has expired... oops... Obviously I don't want to pay for Enterprise licenses if I don't need them, so I'm looking for a way to get to SQL Standard. I have found some information about moving SCCM Sites to a new SQL server but am a bit nervous doing that from what I've read on how picky SCCM is with not changing SQL stuff. I have a guy here who is a bit of a SQL guru that feels like we should be able to migrate to a new SQL database pretty smoothly, but I'm a tad skeptical since he doesn't know much, if anything, about SCCM. My thought was to build a new hierarchy and use the built in migration feature of SCCM 2012 R2 to move data to the new hierarchy. Are there any caveats to the migration? Are there things that can't be transferred using a migration job? Will I have to re-install all of our clients once we migrate? Has anyone done this, or could anyone provide some insight on which route to pursue? I'm leaning more towards the migration since it's built into SCCM and it is meant to do that sort of thing, rather than trying to rip the SQL DB out from behind SCCM and trying to connect it to a new instance. Thanks in advance for any help.
  14. I have been playing with the side by side migration tool in sccm 2012 and have a few questions. I built a test lab (lab.local 1X DC - win2008r2 running dhcp and dns 1X sccm 2007 sp2 r3 server 1X sccm 2012 r2 server I then went and configured sccm 2007 to do the following, which all work fine OSD , build, capture, patch at build Application delivery (single flash player application) Then built an sccm 2012r2 server (local sql etc) Ran the migration tool and specified the source hierarchy. This all worked well, found items to migrate etc. I then migrated various test bits, boundary, collection, and package. I noticed my package had migrated by the package source was still located on the sccm 2007 server. If I were to decommission the sccm 2007 server, this would then break. Do I need to manually recreate a package source, manually populate (copy) the source files / applications / packages across. - Then migrate and manually adjust the package source on the sccm 2012 server to point to the new package source and redistribute ? Any experience or pointers would be nice, as the tool itself looks to be really useful. Just wondering if I have missed something ?? Any pointers appreciated ! Regards WAZZIE
  15. I have successfully migrated one 2007 R2 secondary site to a new SCCM 2012 DP, but "Microsoft System Center Configuration Manager 2007 R2" is still showing in "Control Panel" - "Program and Features" (Windows 2008). I tried to uninstall after rebooting the server, but there is the following error: Service 'SMS_SITE_COMPONENT_MANAGER' (SMS_SITE_COMPONENT_MANAGER) failed to start. Verify that you have sufficient privileges to start system services.
  16. We recently moved from 2007 to 2012 R2... as in 1 week after R2 release. Our consultant didn't know a ton about R2 so we had a few hiccups. I'm going to detail them here and see if any of you have any thoughts. SILVERLIGHT We have a sliverlight app that will not print on anything more advanced then silverlight 4. So we decided not to deploy silverlight with the client. Works fine... doesn't last a long time. Silverlight would upgrade or install (if not present) after a day or two. This is with us setting silverlight to NO update (app and registry and GPO) and not having it as part of the updates we download from WSUS. Not everyone uses the SL app but since we can't keep SL from upgrading if they do, we are stuck with two SCCM for the moment. This si problematical at best and using up resources we want to recover. OSD TS Deployment of Applications We have a number of task sequences that deploy a mixture of applications and packages. Even though the app will deploy afterwards we have occasional issues where a app will not install as part of the task sequence and there is no indication of anything wrong in the SMSTS.log file. Acts like the app was installed but its not. And if you check all the apps are on the local DP (and validated)... and as I said, I can deploy the app afterwards either separately or as part of another application TS. This tends to happen mostly to APPS, not packages. Office, Streets & Trips, Citrix reciever and a few others. And I'll have two identical machines, running on same port (different time) and one will get everything and one will miss half the apps. Also tried identical machines same time, different ports of same switch with same mixed results. These are all apps built form migrated packages; at most we went in and changed detection method after migration and conversion. Migrated apps and driver packages I am NOOB at SCCM, so forgives the NOOBNESS of this statement. I thought that if I took a TS and tried to Distribute Content to a DP or DP group and couldn't then all the apps and drivers were there and working. Same for driver and software packages; I thought if you distributed and didn't hear back, all was good. I found out I was wrong when we sent a DP to a remote site with limited bandwidth and realized the DP was falling back to boss SCCM box in our data center for a lot of (formerly migrated) software and driver packages. Upon diving in I found a good chunk of the migrated packages would not validate and ended up rebuilding the package (for software) and then redeploying (same source for software, same commands and settings just built into a package rather then migrated) and it worked. I am now looking at rebuilding most of our software and driver packages that were migrated. 0 Size Driver packages I have a number of newly created driver packages that have zero size. I have seen some posts on this but I have not seen a definitive answer. is this a error or is it indicative that the drivers are in other packages? 2007 Pushes We still have the bulk of the user base on 2007. However, most of the DPs (1 per AD site) have been moved to 2012 and do not work with 2007 anymore. I occasionally have clients in other AD sites fail to get software (will process when downloaded but never downloads). Should l recreate boundaries for each AD site and include the data center DP as a protected DP for each boundary? I have more issues that I am struggling with but this is enough for now. Any assistance, be they references to other posts or new wisdom, appreciated. Thanks!
  17. Hi, i need to migrate a number of cm07 osd task sequences to cm12 and they fail everytime on incompatible steps as i have mdt2010 installed on the cm07 primary. I wondered if anyone can advise on the easiest way to migrate these please? i've read that the easiest way is to: 1. upgrade cm07 to mdt 2012u1, 2. upgrade all the cm07 TS, 3. install and integrate mdt2012u1 to the cm12r2 primary, 4. and then migrate TS from cm07 to cm12r2, is this right or is there a better way? and can anyone point me to some instructions on the upgrade of mdt2010 to mdt2012u1 as well as how to upgrade the TS on cm07? i ask because i've read that it can be tricky to do! thanks.
  18. Good morning, I have printers set for inventory on my SCCM 2012 environment. I need to run a query on all USB/LPT connected printers in the district. Can someone please help me with a query/report or something that I can run that will give me a list of all printer models that have been collected from all my clients? This will help me in collecting drivers while we go forward with our district-wide windows 7 migrations. Many thanks!
  19. Published: 2013-08-07 (at testlabs.se/blog) Updated: - Version: 1.0 This post will focus on migrating Groups, Mail-In databases and Resources from Domino/Notes migration to Exchange On-premise or Office 365. Before going into any details, if you are planning to do a migration from Domino and want to use Dell Software’s Notes Migrator for Exchange, it is important to mention that there is a requirement from the vendor to use certified people for the project. This blog post is based on Notes Migration for Exchange version 4.7.0.82. Read the other parts: Part 1: Migrations – Overview Part 2: Prerequisites for Domino/Notes migrations Part 3: Migrating Domino/Notes to Exchange 2013 On-premise Part 4: Migrating Domino/Notes to Office 365 Part 6: Prerequisites for Coexistence between Domino and Exchange 2013/Office 365 Part 7: Configuring Quest Coexistence Manager for Notes with Exchange 2013 On-premise Part 8: Configuring Quest Coexistence Manager for Notes with Office 365 Part 9: Prerequisites for Quest Migration Manager Part 10: Migrating User Mailboxes from Exchange 2003 to Exchange 2013 using Migration Manager Part 11: Migrating User Mailboxes from Exchange On-premise to Office 365 Installation Notes Migrator for Exchange (NME) The installation is a regular next/next/finish installation. During the first startup it will ask for a license file, so provide an appropriate license and the application will start. The installation and configuration instructions can be found at: http://www.testlabs.se/blog/2010/11/19/lotus-domino-exchange-2010-in-lab-part-2/ Creating batches/collections Creating batches of Groups is done through “Group Collections – Manage” and the “New collection…” option. Creating batches of mail-in databases and resources works the same way, following the steps below. Users are migrated based in batches (or collections), these batches are created through “User Collections – Manage” and pressing “New collection…”. Provide a collection name and label (label is not required). Labels can be very helpful when looking for a particular batch after creating many collections. Designating users for each batch can be done either by finding them in the directory (i.e. NME database) or by importing from a TSV file. In this example, I select from the directory because I am only selecting one user. In other cases, the TSV import may be useful. As demonstrated below, I search for a user with a Display Name that starts with Jonas. Type the desired characters in the value field, press “Add” button. You can add multiple criteria to the search filter if desired and press “Find now” when ready. The results will be shown in the search result section. Select the desired user(s) and press “OK”. The user is then added into the batch. For illustration, the picture below shows a collection of Groups. Migration finalization / switch / routing Updating routing for groups, mail-in databases and resources works almost the same as user routing. Migrations are accomplished by switching the routing and migrating the contents. NME will configure the objects with appropriate forwarding settings to ensure Domino can route email to Exchange for this specified forwarding domain. See section Notes from the field for configuring Domino mail routing. Before any changes are made, it’s good to have insight of how the objects look in Domino Administrator. See the pictures below. For more information about the objects, an LDAP browser can be used. I recommend Softerra LDAP Browser 4.5. Rooms Room100 – Restricted room “specific people”, can only be booked by the listed people. Room101 – “Owner only”, only owners are allowed to book the room, others requires owner approval. Room102 – No restrictions See the picture below for total summary of the Domino restriction settings (source: Dell Software: Pre-migration planning guide). Room switching / routing / migration From “User Collections – Migrate User Data”, select the migration batch by pressing the arrow and choosing the desired batch. When selected, press “Migrate…” Select “Manage mail routing” and press “Next”. Select “Exchange” and “Quest Coexistence Manager for Notes” with “Using ActiveMail processing”. This will configure the associated Domino object with a forwarding address. “Calendar domain: Exchange” (this is used during Freebusy coexistence, discussed in coexistence post) ”Set server running qcalcon: dominoserver/dominodomain” (specify the server that have Qcalcon installed) ”Specify your Domino domain: dominodomain” (specify your Domino domain) Check “Set mail forwarding address” ”Forwarding mail domain: exchange.testlabs.se” (Domino need to route mails to this SMTP domain) Select ”Append Domino domain to forwarding address” ”Overwrite existing mail forwarding address: Always” Then press “Next”. If Exchange mailboxes have forwarding/targetAddresses configured, these can be removed using this option as well. In my test case, I don’t have these configured, so I will let them be unchecked. Press “Next”. When switching (routing) mailboxes, with sufficient hardware, I typically run this operation with at least 20 threads (simultaneous processes). However, in this scenario it is being performed on a couple of mailboxes, so I left it with 1 thread. Press “Next”. A summary is shown, press “Next”. The operation can be scheduled but, in my case, I want to run it now. Press “Next”. The operation starts… …and it was completed. Press “Exit”. When the operation is complete, you can verify that the object in Domino directory has been updated. Note that the Forwarding address (known as “mailaddress”) now is configured, the Mail system (known as “mailsystem”) is configured to Other Internet Mail (has a value of “5”) and Domain value has been deleted. Migrating data Since the mail routing is complete and new mail will route directly to the Exchange mailbox, it’s time to migrate the data. One thing to keep in mind before starting the migration, is verifying the mailboxes were created with the correct mailbox type. In this scenario it should be created as “Room Mailbox”. This can be verified by running the PowerShell command: Get-Mailbox room* | ft DisplayName,Resourcetype –Autosize If they were listed as User Mailboxes for some reason, they could easily be changed to Room Mailboxes by running the PowerShell command: Get-Mailbox room* | Set-Mailbox –Type Room Similarly, for Mail-In databases to Shared Mailboxes, verify they are listed as shared mailboxes. If needed, change the type by running the PowerShell command: Get-Mailbox mail-in-databases* | Set-Mailbox –Type Shared Before the migration, one of the target mailboxes had 1 item and a total of 4 kb. All others had zero items, shown in the picture below. Using PowerShell command: Get-Mailbox room* | Get-MailboxStatistics | ft displayname,itemcount,totalitemsize –Autosize Go to “User Collections – Migrate User Data”, select the migration batch and press “Migrate…” Select “Migrate mailbox data”, press “Next”. In this scenario, I didn’t use the notification options. However, these can be helpful for letting users know that they are migrated and should start to use Outlook instead of Notes. Press “Next”. Select the data types you wish to migrate. I decide not to migrate Trash and the Archive. Everything else will get migrated. Press “Next”. Select the preferred conversion method for DocLinks. For this example, I used “Notes .NDL attachment (requires Notes client to use after migration)”. Press “Next”. Select “Through Domino server(s)”, press “Next”. Select “Server-based mailbox”, press “Next”. In my scenario, I want to migrate everything, but the filtering options can be very useful in projects that might require migrating (or pre-migrating) a subset by date or size. After selecting the appropriate settings, press “Next”. When migrating mailbox data, I commonly run it with 8-12 threads (simultaneous processes). You will need to determine the setting that is best in your environment. This is normally done before or during the pilot phase of the project to ensure the optimal configuration is ready for production migrations. In this scenario, I am just migrating three resources so I leave it with 1 thread. Press “Next”. A summary is shown, press “Next”. I want to start the migration now. However, if that’s not the case, you have the opportunity to schedule it. Press “Next”. The operation starts… …during the operation… …operation completed. Press “Exit”. For this example, the migration throughput rates are low because we migrated a couple of test mailboxes with a small sampling of data. As you scale your migrations to include additional mailboxes and threads, much higher throughput rates will be achieved. This was done in a lab environment using slow disks and small amount of memory. When the migration is completed, I recommend comparing item counts and mailbox sizes, but you will need to account for data compression differences between Domino and Exchange. I’ve seen differences between 20-35% depending on the circumstances. This means a Notes mail file of 1 GB may be 1,35 GB in Exchange. However, this is just a rule of thumb and needs to be estimated with actual data from each project since every customer is unique. Verify the item count and mail data size by using the same PowerShell command: Get-Mailbox room* | Get-MailboxStatistics | ft displayname,itemcount,totalitemsize –Autosize The picture below shows that there are now a total of 5 items and 17 kb of data in the mailboxes. Group migrations We created one Group collection/batch at the beginning of this article. For illustration the two Groups will be migrated into Active Directory (AD) / Exchange. The first group, called “Finance”, is a Multi-purpose group (could be compared with Security Group in AD) that could not only be used for mail but also controlling permissions. The second group called “Marketing”, is Mail-only group, which could be compared to a Distribution Group/List in Exchange and is only used for distribution mails. ‘ Let’s start the provisioning process within “Group Collections – Provision”. Select the desired group collection and press “Provision groups…” Verify the Group Type for the collection and the path are correct. Also, verify the container for external contacts is correct. Check the option “Keep groups in sync with corresponding Notes groups”, this option will make sure that the group is updated with the correct members. Press Next. A summary is shown, press Next. I want to run the task Now, press Next. The result is shown. Press Exit. Groups were created successfully in the correct OU. Verify the members are correct. Looks fine… The owner/manager (ManagedBy) is also migrated over. If groups are updated in Domino on a regular basis and they need to be maintained in AD/Exchange, a scheduled job could be created to automate this process. Information about how to create a scheduled job can found in the Administration Guide of NME included with the software. Permissions / Delegation / Restrictions during migrations The following quote from the User Guide regarding migration of delegated users outlines the prerequisites quite well for getting the delegates over to Exchange. The permissions on normal Domino mailboxes are migrated IF the prerequisites above are fulfilled. I would like to recommend investigating both the Resources and the Mail-In databases regarding restrictions, who has permissions to book and who is the owner before starting the migration. This can either be done in Domino or using an analyzer tool, like MessageStats. Changes regarding migration of delegates have been made in the last version of NME (version 4.7.0.82). These optional variables has been added and could be used, more information can be found in the release notes for NME. [Exchange] MigrateResourceDelegation=<#> GrantResourceOwnerFullAccess=<#> MigrateMailInDBOwner=<#> Notes from the field Dell Software – MessageStats – The tool can be of great value for analyzing and investigating environments before starting migrations. More information is available here: http://www.quest.com/messagestats/ Domino SMTP routing – This can be difficult to understand if you haven’t been working with Domino or been involved in any migration projects before. I posted an article about coexistence that goes through the configuration steps: http://www.testlabs.se/blog/2011/01/03/coexistence-between-domino-and-exchange-2010-%e2%80%93-part-1-of-2/ Proxy server – One thing that can be a potential issue during migrations is proxy servers. I recommend avoiding them as much as possible. If you can avoid them you will most likely save yourself some issues that might occur if a proxy server is used. These tend to block or throttle traffic, the impact can be either that the migration throughput will be very low or that it will prohibit the traffic from reaching its destination. Creating batches/collections – If you are involved in larger migration projects, you likely won’t want to find each user manually. As an alternative, you can search by a Domino Directory value that is unique to each migration batch. Another method for adding users to the batch is using TSV files. If you choose this approach, Excel will become your best friend. Pre-stage/Delta migration consideration – In cases where it’s possible, I recommend starting the migration right away after the pilot has been approved. This means that the mailbox data can be migrated over/synchronized before the actual migration must take place. By pre-staging data, the mailbox switch/routing can be done fast and finally the mailbox delta data (differences) can be migrated. This can minimize the “migration time”. By this, I mean the time that the end-users are impacted in some way or another. One thing to keep in mind if using this method is that as soon as a mailbox is created in Exchange, the Free/Busy requests from other Exchange users sent to this newly created user won’t be sent back to Domino (where the most current data remains and action should take place). I have requested a feature from Microsoft that would make the “forwarding” of Free/Busy requests possible, but haven’t heard anything back from them yet. It would be great if that could be solved, probably easily by using targetAddress attribute together with a new attribute, for ex. forwardfbreq set to either 0 (default) or 1. Don’t hesitate to comment if you would like to add anything or if you have other experiences, I will add it into the post and link your blog. Next post will be published after the holidays, in the meanwhile enjoy the vacations stay tuned after summer for new publications, we I start of with Coexistence Manager for Notes.
  20. Published: 2013-06-21 (at testlabs.se/blog) Updated: - Version: 1.0 This post will focus on migrating Domino/Notes to Exchange 2013 On-premise. Before going into any details, if you are planning to do a migration from Domino and want to use Dell Software’s Notes Migrator for Exchange, it is important to mention that there is a requirement from the vendor to use certified people for the project. This blog post is based on Notes Migration for Exchange version 4.7.0.82. If you would like to read the other parts see the section “See the other parts” Installation Notes Migrator for Exchange (NME) The installation is a regular next/next/finish installation. During the first startup it will ask for a license file, so provide an appropriate license and the application will start. The installation and configuration instructions can be found at: http://www.testlabs.se/blog/2010/11/19/lotus-domino-exchange-2010-in-lab-part-2/ Creating batches/collections Users are migrated based on batches (or collections), these batches are created from “User Collections – Manage” and by pressing “New collection…” Give the collection a name and label (label is not required). Labels can be of great help if looking for a particular batch after creating many collections. Choosing which users that should reside in the batch can be done either by finding them in the directory (i.e. NME database) or by importing them from a TSV file. In this example, I chose find them from the directory because I only select one user. In other cases the TSV import can be useful. As demonstrated below, I search for a user with a Display Name that starts with Jonas. Type the desired characters in the value field, press “Add” button. You can add multiple criteria to the search filter if desired and press “Find now” when ready. The results will be shown in the search result section. Select the desired user(s) and press “OK”. The user is then added into the batch. Migration finalization / switch / routing When migration batches/collections have been created we are ready to start the migration. It is basically done by switching the mailbox and migrating the contents. NME will configure the Domino person document with appropriate forwarding settings to ensure Domino can route email to Exchange for this specified forwarding domain. See section Notes from the field for how to configure Domino mail routing. Before any changes are made, the mailbox properties typically looks like the picture below. It has an Internet Address (same as email addresses in Exchange i.e. SMTP). Go to “User Collections – Migrate User Data”, select the migration batch by pressing the arrow and choosing the correct batch. When selected, press “Migrate…” Select “Manage mail routing” and press “Next”. Select “Exchange” and “Quest Coexistence Manager for Notes” with “Using ActiveMail processing”. This for configuring the Domino mailbox with a forwarding address. “Calendar domain: Exchange” (this is used during Freebusy coexistence, discussed in coexistence post) ”Set server running qcalcon: dominoserver/dominodomain” (specify the server that have Qcalcon installed) ”Specify your Domino domain: dominodomain” (specify your Domino domain) Check “Set mail forwarding address” ”Forwarding mail domain: exchange.testlabs.se” (Domino need to route mails to this SMTP domain) Check ”Append Domino domain to forwarding address” ”Overwrite existing mail forwarding address: Always” Then press “Next”. If Exchange mailboxes have forwarding/targetAddresses configured, these can be removed by using this option. In my case I don’t have these configured, so I will let them be unchecked. Press “Next”. When switching (routing) mailboxes, with sufficient hardware, I typically run this operation with at least 20 threads (simultaneous processes). However, in this scenario it is being performed on a single mailbox, so I left it with 1 thread. Press “Next”. A summary is shown, press “Next”. The operation can be scheduled but, in my case, I want to run it now. Press “Next”. The operation starts… …and it was completed. Press “Exit”. When the operation is complete, look at the user in Domino directory, it is a bit different. Note that the Forwarding address now is configured, the Mail system is configured to Other Internet Mail and Domain value is empty. Migrating data Since the mail routing is completed and all new mail will route directly to the Exchange mailbox, it’s time to migrate the data. Before the migration was started, the mailbox only had 4 items and a total of 254 kb, shown in the picture below. Using PowerShell command: Get-MailboxStatistics jonand | ft displayname,itemcount,totalitemsize –Autosize Go to “User Collections – Migrate User Data”, select the migration batch and press “Migrate…” Select “Migrate mailbox data”, press “Next”. In this scenario, I didn’t use the notification options. However, these can be helpful for letting users know that they are migrated and should start to use Outlook instead of Notes. Press “Next”. Select data types you wish to migrate, I decide to not migrate Trash and the Archive. Everything else will get migrated. Press “Next”. Select the preferred conversion method for DocLinks. For this example, I used “Notes .NDL attachment (requires Notes client to use after migration)”. Press “Next”. Select “Through Domino server(s)”, press “Next”. Select “Server-based mailbox”, press “Next”. In my scenario I want to migrate everything, but the filtering options can be very useful in projects that might require to just migrate the last year’s contents and not attachments that are over 10 MB. When you have select the appropriate settings, press “Next”. When migrating mailbox data, I commonly run it with 8-12 threads (simultaneous processes). You will need to determine the setting that is best in your environment. This is normally done before or during the pilot phase of the project to ensure the most optimal configuration is ready for production migrations. In this scenario, I am migrating a single mailbox so I leave it with 1 thread. Press “Next”. A summary is shown, press “Next”. I want to start the migration now. However, if that’s not the case, you have the opportunity to schedule it here. Press “Next”. The operation starts… …during the operation… …operation completed. Press “Exit”. For this example, the migration throughput rates are low because we migrated a single mailbox with a small sampling of data. As you scale your migrations to include additional mailboxes and threads, much higher throughput rates will be achieved. This was done in a lab environment using slow disks and small amount of memory. When the migration is completed, it’s a good recommendation to compare item counts and mailbox size, but you will need to account for data compression differences between Domino and Exchange. I’ve seen differences between 20-35% depending on the circumstances. This means a Notes mail file of 1 GB may be 1,35 GB in Exchange. However, this is just a rule of thumb and needs to be estimated with actual data from each project since every customer is unique. Verify the item count and mail data size by using the same PowerShell command: Get-MailboxStatistics jonand | ft displayname,itemcount,totalitemsize –Autosize The picture below shows that there are now 51 items and the mailbox holds 886 kb. Notes from the field Domino SMTP routing – This can be difficult to understand if you haven’t been working with Domino or been involved in any migration projects before. I did post an article about coexistence that goes through the configuration steps, read it here: http://www.testlabs.se/blog/2011/01/03/coexistence-between-domino-and-exchange-2010-%e2%80%93-part-1-of-2/ Proxy server – One thing that can be a potential issue during migrations is proxy servers. I recommend avoiding them as much as possible. If you can avoid them you will most likely save yourself some issues that might occur if a proxy server is used. These tend to block or throttle traffic, the impact can be either that the migration throughput will be very low or that it will prohibit the traffic from reaching its destination. Creating batches/collections – If you are involved in larger migration projects, you likely won’t want to find each user manually. As an alternative, you can search by a Domino Directory value that is unique to each migration batch. Another method for adding users to the batch is using TSV files. If you choose this approach, Excel will become your best friend. Precopy/Delta migration consideration – In cases where it’s possible, I recommend starting the migration right away after the pilot has been approved. This means that the mailbox data can be migrated over/synchronized before the actual migration must take place. By pre-staging data, the mailbox switch/routing can be done fast and finally the mailbox delta data (differences) can be migrated. This can minimize the “migration time”. By this, I mean the time that the end-users are impacted in some way or another. One thing to keep in mind if using this method is that as soon as a mailbox is created in Exchange, the Free/Busy requests from other Exchange users sent to this newly created user won’t be sent back to Domino (where the most current data remains and action should take place). I have requested a feature from Microsoft that would make the “forwarding” of Free/Busy requests possible, but haven’t heard anything back from them yet. It would be great if that could be solved, probably easily by using targetAddress attribute together with a new attribute, for ex. forwardfbreq set to either 0 (default) or 1. Read the other parts Part 1: Migrations – Overview Part 2: Prerequisites for Domino/Notes migrations Part 4: Migrating Domino/Notes to Office 365 Part 5: Migrating Resources Mailboxes, Mail-In databases and Groups Part 6: Prerequisites for Coexistence between Domino and Exchange 2013/Office 365 Part 7: Configuring Quest Coexistence Manager for Notes with Exchange 2013 On-premise Part 8: Configuring Quest Coexistence Manager for Notes with Office 365 Part 9: Prerequisites for Quest Migration Manager Part 10: Migrating User Mailboxes from Exchange 2003 to Exchange 2013 using Migration Manager Part 11: Migrating User Mailboxes from Exchange On-premise to Office 365 Feel free to comment the post, I hope you liked the information. If you find something that might be incorrect or you have other experiences, leave a comment so it can be updated.
  21. Hi Gurus , I would like to come up with a design for SCCM 2012 as I think it is a good time to migrate from SCCM 2007. I am planning to do it on Server 2012 and SQL 2012. I have a management forest, and multiple forest’s below this with only a one way trust (the management forest does not trust anything). I currently run SCCM 2007 and have a Central Site with Primary Sites nested below this. Sincethis is not supported in 2012 and the Primary Site with Secondary Sites nested below is not supported across untrusted domains I have hit a snag and want to make sure my design will work. From what I read, we do not have near enough servers to manage to require a CAS, although this is the case would our inter forest environment require a CAS to manage multiple un-trusted forests? I was thinking of installing a primary site and then installing management roles on a server in each forest that we will be managing. Would that be a good start? Please keep in mind that we would also like to integrate Forefront Endpoint Protection into this design. With this design, would I need a SQL server in each of the domains? I am also wondering if the following site roles would be enough for a management server in each forest? Management Point Distribution Point Software Update Point I would greatly appreciate your help as I don’t want to implement a flawed design
  22. This script idea came up after being involved in a migration project. Published: 2013-05-22 Updated: 2013-05-24 Version: 1.1 It’s purpose with this script is for getting Quest Migration Manager (QMM) being able to match objects between domains. In a scenario with one-way trust and not being able to use Quest Migration Manager AD or any other tool for providing the SIDHistory into the AD objects. Users, mailboxes and mail contacts are already created, where the contacts are used for having a global address list (GAL) object they can send emails to. Using QMM you can match by Username, Mailaddress or SIDHistory. In my case the username differs and the SIDHistory is not available (not allowed being copied into the target AD). I created four different functions within this script, one called “Export-SourceInformation”, which should be used in the source environment. It will export the information from the source regarding Name, DisplayName, PrimarySmtpAddress, RecipientTypeDetails and save it into a CSV file called “users.csv”. Then bring the CSV file into the target environment. This CSV file should be used as a control file if you don’t want to run all users at the same time (run some tests before running all of them in one batch). I would recommend a couple of smaller batches for testing the functions before deploying it in full scale. There is a function called “Verify-TargetInformation”, which uses the CSV file called “users.csv” and retrieves the Name and PrimarySmtpAddress for each object in the CSV file. Another function is called “Set-SourceAddress”, this part takes care of the target account. It uses the file called “users.csv” and checks whether there are any contacts for these mailboxes, if there are the mail contact will be deleted and the mailbox forward settings will be removed together with making sure that the mailbox is showed in the GAL. But before any changes are done, the current configuration for both the mail contact and the mailbox object are being saved into a CSV file called “targetinformation.csv”. Last but not least, the function called “Rollback-TargetInformation” is used for putting back the PrimarySmtpAddress to the value that it was prior to the change, this by using the CSV file “targetinformation.csv”. When the Directory Synchronization have successfully matched the mailboxes this function should be runned for having back the correct information. You can use this for free, without any guarantee or warranty and at your own risk. Feel free to post about it, just make sure to link my blog and blogpost. Download the script ##################################################################################### # Filename: Migration-Preparation-testlabs.ps1 # Description: # This PowerShell script exports information, configures objects and prepares for # Quest Migration Manager EX Directory Synchronization # # Usage: Import-Module Migration-Preparation-testlabs.ps1 # Start with importing the module, then Starting function: Export-SourceInformation; # Set-SourceAddress; Rollback-TargetInformation; Verify-TargetInformation # # Version: 1.1 # # Changelog: # v1.1 - Introduced LegacyExchangeDN - X500 migration # # Jonas Andersson, MCC 2011 & 2012 # http://www.testlabs.se/blog # Twitter @jonand82 ##################################################################################### Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010 -ErrorAction SilentlyContinue Add-PSSnapin Microsoft.Exchange.Management.PowerShell.Admin -ErrorAction SilentlyContinue ## Exporting the SMTP information from Source mailboxes Function Export-SourceInformation(){ $filename = "users.csv" $users = Get-Mailbox -resultsize unlimited | Select Name,DisplayName,PrimarySmtpAddress,RecipientTypeDetails,LegacyExchangeDN $users | Export-CSV $filename -notype -Encoding Unicode } ## Changing Target mailboxes to Source PrimarySmtpAddress for QMM to match on it Function Set-SourceAddress(){ $data = Import-CSV .\users.csv $filename = "targetinformation.csv" ## Saving Target Information into CSV file before changing $MasterList = @() Foreach($t in $data) { $str = $t.displayname $MyObject = New-Object PSObject -Property @{ Name = (Get-Mailbox -resultsize unlimited -Filter "DisplayName -like '*$str*'").Name DisplayName = (Get-Mailbox -resultsize unlimited -Filter "DisplayName -like '*$str*'").DisplayName PrimarySmtpAddress = (Get-Mailbox -resultsize unlimited -Filter "DisplayName -like '*$str*'").PrimarySmtpAddress RecipientTypeDetails = (Get-Mailbox -resultsize unlimited -Filter "DisplayName -like '*$str*'").RecipientTypeDetails Email = ((Get-Mailbox -resultsize unlimited -Filter "DisplayName -like '*$str*'").EmailAddresses -Join ";") DeliverToMailboxAndForward = (Get-Mailbox -resultsize unlimited -Filter "DisplayName -like '*$str*'").DeliverToMailboxAndForward ForwardingAddress = (Get-Mailbox -resultsize unlimited -Filter "DisplayName -like '*$str*'").ForwardingAddress ForwardingSmtpAddress = (Get-Mailbox -resultsize unlimited -Filter "DisplayName -like '*$str*'").ForwardingSmtpAddress HiddenFromAddressListsEnabled = (Get-Mailbox -resultsize unlimited -Filter "DisplayName -like '*$str*'").HiddenFromAddressListsEnabled LegacyExchangeDN = (Get-Mailbox -resultsize unlimited -Filter "DisplayName -like '*$str*'").LegacyExchangeDN ContactName = (Get-MailContact -resultsize unlimited -Filter "DisplayName -like '*$str*'").Name ContactDisplayName = (Get-MailContact -resultsize unlimited -Filter "DisplayName -like '*$str*'").DisplayName ContactPrimarySmtpAddress = (Get-MailContact -resultsize unlimited -Filter "DisplayName -like '*$str*'").PrimarySmtpAddress ContactEmail = ((Get-MailContact -resultsize unlimited -Filter "DisplayName -like '*$str*'").EmailAddresses -Join ";") ContactExternalEmailAddress = (Get-MailContact -resultsize unlimited -Filter "DisplayName -like '*$str*'").ExternalEmailAddress ContactHiddenFromAddressListsEnabled = (Get-MailContact -resultsize unlimited -Filter "DisplayName -like '*$str*'").HiddenFromAddressListsEnabled } $MasterList += $MyObject } $MasterList | Export-Csv $filename -NoTypeInformation -Encoding Unicode Write-Host "Information is saved into the CSV file: $filename" -ForegroundColor White Foreach($i in $data) { $str = $i.displayname ## Removing mail contacts for Source users $c = Get-MailContact -resultsize unlimited -Filter "DisplayName -like '*$str*'" Write-Host $c -ForegroundColor Yellow ## Multiple matching, no changes will be done if ($c.count -ge 1) { Write-Host "ERROR: Multiple matching" Write-Host "Matches: $c.count" return } ## Unique contact found, removing it if ($c.count -eq $null) { Write-Host "Unique matching: $c" Write-Host "Removing the mail contact object for: $c" Remove-MailContact -Identity $c -Confirm:$false } ## Starting the configuration for Target Mailboxes $u = Get-Mailbox -resultsize unlimited -Filter "DisplayName -like '*$str*'" Write-Host $u -ForegroundColor Yellow ## Multiple matching, no changes made if ($u.count -ge 1) { Write-Host "ERROR: Multiple matching" Write-Host "Matches: $u.count" return } ## Setting the Source PrimarySmtpAddress on the Target Mailboxes if ($u.count -eq $null) { Write-Host "Unique matching: $u" Write-Host "Setting Source SMTP as PrimaryAddress for matching using QMM" Write-Host "Configuring the mailbox for showing up in GAL and remove the forwarding configuration" Write-Host "Adding the LegacyExchangeDN as X500 for Outlook auto-complete cache" $email = $i.PrimarySmtpAddress $x500 = $i.LegacyExchangeDN Set-Mailbox -Identity $u -ForwardingAddress $null -DeliverToMailboxAndForward:$false -HiddenFromAddressListsEnabled:$false -PrimarySmtpAddress $email -EmailAddressPolicyEnabled:$false $ProxyAddresses = (Get-Mailbox -Identity $u).EmailAddresses $ProxyAddresses += [Microsoft.Exchange.Data.CustomProxyAddress]("X500:$x500") Set-Mailbox -Identity $u -EmailAddresses $ProxyAddresses } else { Write-Host "No match" return } } Write-Host "" Write-Host "#################################################################" -ForegroundColor White Write-Host "# First run the Verify-TargetInformation.. #" -ForegroundColor White Write-Host "# Start the QMM Synchronization for matching Source <-> Target #" -ForegroundColor White Write-Host "# Finally run the Rollback-TargetInformation when sync is done #" -ForegroundColor White Write-Host "#################################################################" -ForegroundColor White Write-Host "" } ## Rollback of Target PrimarySmtpAddress Function Rollback-TargetInformation(){ $data = Import-CSV .\targetinformation.csv $MasterList = @() Foreach($i in $data) { $str = $i.displayname $user = Get-Mailbox -resultsize unlimited -Filter "DisplayName -like '*$str*'" ## Predicts there is only one @testlabs.se address $pri = Get-Mailbox -Identity $user | Select-Object -ExpandProperty EmailAddresses | Where-Object {$_.SmtpAddress -like '*@testlabs.se'} | Select-Object SmtpAddress $adr = $pri.SmtpAddress Write-Host "Configuring mailbox: $user with adress: $adr" -ForegroundColor White Set-Mailbox -Identity $user -PrimarySmtpAddress $adr -EmailAddressPolicyEnabled:$False } } ## Verifying the Target PrimarySmtpAddress Function Verify-TargetInformation(){ $data = Import-CSV .\users.csv $filetime = (get-date -format yyyyMMdd-hhmm) $filename = "verify-$filetime.csv" $MasterList = @() ## Verifying the PrimarySmtpAddress Foreach($i in $data) { $MyObject = New-Object PSObject -Property @{ Name = (Get-Mailbox -Identity $i.PrimarySmtpAddress).Name PrimarySmtpAddress = (Get-Mailbox -Identity $i.PrimarySmtpAddress).PrimarySmtpAddress Database = (Get-Mailbox -Identity $i.PrimarySmtpAddress).Database EmailAddresses = ((Get-Mailbox -Identity $i.PrimarySmtpAddress).EmailAddresses -Join ";") } $MasterList += $MyObject } $MasterList | Export-Csv $filename -NoTypeInformation -Encoding Unicode Import-CSV $filename Write-Host "" Write-Host "SMTP Verification is saved into the CSV file: $filename" -ForegroundColor White Write-Host "" }
  23. Good Afternoon, I have currently have SCCM 2012(thanks to your SCCM guides) setup in my test environment. However, on my production environment we currently have SCCM 2007 in production and planning on moving/migrating over to SCCM 2012 the next few months. Now, is it necessary to create a SCCM 2007 environment in my test environment to successfully test the migration? Which would mean I would have to scrap my current SCCM 2012 and start all over again.... Or should I just keep on current SCCM 2012 in test and work from there, since you can only stand up SCCM 2012 in parallel (no upgrade function) with SCCM 2007. Also, I was thinking of not using any of the migration tools. Thanks, Paul
  24. Hey everyone, Happy survival of the Maya end of days! hehe. I've been looking at the SP1 beta of sccm 2012 in my lab, and also read up some on it, and i found some information that says the following: "More flexible hierarchy management with support to expand a stand-alone primary site into a hierarchy that includes a new central administration site, and the migration of a Configuration Manager SP1 hierarchy to another Configuration Manager SP1 hierarchy. (Source: http://technet.micro...ibrary/jj591552) From what i can understand, this means that you should be able to join a hierarchy currently only using a Primary Site as a top, to a CAS structure, without starting from scratch. I've got 2 separate hierarchy's in my LAB (One CAS with a Primary, and one Primary StandAlone), but i can't really seem to find out how this can be done. Is it just me thats looking in the wrong places, or have i miss-understood what they mean by this? Hope you all have a great christmas Best regards Eirik // Xandor
  25. Hello, If my current SCCM 2007 R2 is installed on a 32bit Windows Server 2003, and I plan on migrating to SCCM 2012 on Server 2008 R2 x64, will there be any problems with the migration process going from a 32bit to 64bit environment? The reason I ask is that I read in a forum post somewhere that an admin in a similar situation did the following steps: performed a full backup of SCCM 2007 running on W2K3 32bit, reinstalled SCCM 2007 on a different server running W2K8 x64 and restored from that backup he made essentially creating a mirrored install but on a x64 OS instead, they then installed SCCM 2012 on the new production server (also W2K8 x64) and finally went into the standard migration steps. This seemed rather convoluted to me, and I found no other posts that claimed there was any need to first mirror your SCCM 2007 from a 32 to a 64bit environment before attempting a full migration to SCCM 2012. Thanks in advance, T
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.