Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

updated references and provide context #1

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

updated references and provide context #1

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ff1f834
updated cmdlets references and provide context
puttyq Oct 11, 2018
96f048c
fix spelling mistakes
puttyq Oct 11, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 9 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,15 +1,19 @@
# FIMDelta
# FIMDelta Background

Helper utility to selectively apply changes between developer and production FIM2010 servers.
Although FIM/MIM does offer the ability for administrators and developers to easily transport configurations between development, testing and production through the use of the [Export-FIMConfig](https://docs.microsoft.com/en-us/powershell/module/fimautomation/export-fimconfig?view=idm-ps-2016sp1) and [Import-FimConfig](https://docs.microsoft.com/en-us/powershell/module/fimautomation/import-fimconfig?view=idm-ps-2016sp1) modules within the [FIMAutomation](https://docs.microsoft.com/en-us/powershell/module/fimautomation/?view=idm-ps-2016sp1) PowerShell module; the mechanism does lack the ability to granularly control specific change. In its standard approach the export, comparison and import of changes via the changes.xml file will transport all changes between environments.

In many cases it is required to just move selected changes into the production environment and this is an ideal use case for FIMDelta.

FIMDelta is a helper utility that allows users to view and to selectively apply changes between developer and production FIM/MIM servers.

![screenshot](screenshot.png)

## Usage

After exporting configurations from both DEV and PROD servers with `ExportSchema.ps1`, and generating delta file with `SynchSchema.ps1`, you copy all 3 files (dev.xml, prod.xml and changes.xml) to the utility directory, and then run it.
After using the standard FIMAutomation cmdlets to exporting configurations from both DEV and PROD servers with `Export-FIMConfig`, and generating delta file with `ConvertFrom-FIMResource`, `Compare-FIMConfig` you copy all 3 files (dev.xml, prod.xml and changes.xml) to the utility directory, and then run it.

Utility will show you all objects in delta as a tree. You can group it either by operation, or by object type.
For a good overview of how to do this and a possible solution on how to automate the export process, see [FIMDelta automation](http://www.mim.ninja/2017/08/17/fimdelta-automation/).

Just check/uncheck objects or single attributes you want to export/skip, and press Save. It will create changes2.xml, which could be applied with `CommitChanges.ps1`.
The utility will show you all objects in delta as a tree and will group them either by operation or by object type. From here you can choose to check/uncheck objects or single attributes you want to export/skip, and press Save. It will create changes2.xml, which could be applied with `Import-FIMConfig`.

The killer feature is reference tracking. If attribute is a reference, it will have referenced objects in a subtree. And if object is referenced by some attribute, it will have "Referenced by" node with all objects referencing it.