FPS Work Instructions

The default source drive and default runtime for FPS can be identical on CI for roaming purposes, but not recommended. Typically, a VM will use a shared location for the source path (default C:\Users\[uid]\OneDrive\FPS) and a local directory (often D:\FPS) for the runtime path. The standard method of setting the source path to roaming mode (making it uniform across all domain related CIs) is documented below.  

To activate the roaming configuration

1. Copy the { FPS:Metadata } directory under the default source location (C:\Users\[uid]\OneDrive\FPS\Metadata) to the offline source location (E:\OneDrive-Roaming\FPS\Metadata).
2. Copy the { FPS:Connectors } directory under the default source location (C:\Users\[uid]\OneDrive\FPS\Containers) to the offline source location (E:\OneDrive-Roaming\FPS\Containers).
3. In E:\OneDrive-Roaming\FPS\ { Metadata:Profile }, a roaming configuration is set up for each Core CI upon initial configuration within $global:pro_Domains. Comment out the standard configuration line and uncomment the roaming configuration line.
3. Copy the roaming profile to the active profile location via the following >> copy E:\OneDrive-Roaming\FPS\MetaData\profile.ps1 C:\Windows\System32\WindowsPowerShell\v1.0\profile.ps1. 
4. The roaming profile is now active. Run a CICD -sync to ensure the runtime is synchronized with the source on all Core CIs within the domain.

To transition from roaming mode back to the standard configuration

1. Replace the standard source direcory (C:\Users\[uid]\OneDrive\FPS\Containers) with the roaming container directory (E:\OneDrive-Roaming\FPS\Containers).
2. Check for MetaData changes between the roaming and standard source directory.  Exclude profile.ps1 as the change was just activating the roaming profile and keep the original source profile.ps1.  Update the source directory with any changes noted.
3. Copy the standard profile to the active profile location via the following >> copy C:\Users\[uid]\OneDrive\FPS\MetaData\profile.ps1 C:\Windows\System32\WindowsPowerShell\v1.0\profile.ps1
4. The standard profile is now active.  Run a CICD -sync to ensure the runtime is synchronized with the source on all Core CI’s within the Domain.

The handle serves as the internal mechanism for identifying the CmdLet within the system on a commented first line – or the status line. When referring to the status line, the handles  will be organized as follows:

 FPS:[Layer 1]{:[Layer 2]:[next layer]}

Shortcuts function as a distinct subsystem, rendering Alias’s as obsolete by enhancing the capabilities. Located in the first module layer with an SC- prefix, shortcuts provide access to all capabilities and services. Pro-Config scans all shortcuts and loads the active version of each noted shortcut regardless of release or version.