nope, that would be expected, you would have to physically import the package into msdb (via SSIS) to se it in msdb.
msdb is usually the better place to store packages, but its not a golden rule, you may want to investigate why the file system has been chosen.
You have a 2 instance cluster which is currently active\passive only because both instances are live on the same node. It is perfectly possible for just one instance to failover in which case you would then be active\active. So reaally its clearer to call it muti-instance.
<?xml version="1.0" encoding="UTF-8"?>
<DtsServiceConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
</Folder> -<Folder xsi:type="SqlServerFolder">
</Folder> -<Folder xsi:type="FileSystemFolder">
I have two named instances (sqlA\instanceA & sqlB\InstanceB) in both nodes (MachineA and MachineB) and I make the following changes in MsDtsSrvr.ini.xml file in both machines.
My deployment method is file system -storing packages on a shared disk (SAN).I made changes as shown above and restarted SSIS services on both the nodes.
However, when I login to SSIS services from Management studion using the hostname (MachineA AND MachineB ), i see packages under filesystem only in MachineA, the same folder is empty on MachineB. Shouldn't the packages be visible there as well? I see two empty MSDB folder on both machines and if try to expand it - I get the extact error as show in the below link even after making changes in the ini file- what i am missing- thanks.