Develop & execute an actionable plan with defined work streams that can guide your organization’s path to cloud adoption. Evaluate your on-premise infrastructure & applications for a cloud readiness, disaster recovery and governance with either single or multi-cloud objectives.
Founded in 2009, Credexo is a Cloud Managed Services Provider that provides strategic consulting & managed services to our customers with a Cloud First, Mobile First mindset.
What do we do?
We have delivered purposeful technology to many of your peers that has totally transformed their businesses and accelerated their growth.
How will you benefit?
Our solutions will help you create new revenue streams so you can disrupt your competition with tools that enable you to achieve faster time to market your new business transformational ideas
You will find our solutions will empower your employees and enables them to adapt to the changing mindset as they adopt your favorite Cloud Platform with automation and protection of digital assets are the key drivers for sustained growth.
FIM Synchronization Service cannot be installed on the same database instance which hosts FIMSynchronizationService database for another instance of FIM Synchronization Service.
This article provides guidance on how to install FIM Sync Service with an existing database.
In-order to have two instance of FIM Synchronization Service instance running, the database needs to be installed on two difference SQL instances.
Microsoft doesn’t recommend have two instance for FIM Sync Service. However, it might be helpful to have two instance for migration of the production instance from code based to code-less provisioning.
Case in point, the production server with provisioning logic built based on the old FIM/MIIS methodology. To keep the production sync running in an uninterrupted manner during this migration, you could install FIM Sync Service, FIM Service & FIM Portal on a different box.
One major difference between the two sync services is only the production will be performing the Exports. This will give enough time for the code-less logic to buildup all the metaverse as all the importing of objects and subsequent application of the new FIM policies might take quite sometime.
Once the metaverse is all built up, the database could be easily migrated to the production FIM Sync server.