Packaging Stuffs

XCACLS: XCACLS or Extended Change Access Control List tool, is an advanced version of CACLS, the difference being that we do not have to answer Yes/No prompts in XCACLS. CACLS and XCACLS are tools which are used to modify the ACLs (Access Control Lists), by which in turn we are modifying the folder permissions for users in windows. CACLS is installed in all users machine in System32 folder. Icacls.exe: This article describes the Icacls.exe command-line utility. You can use this utility to modify NTFS file system permissions Icacls is a better option than LockPermission Table. This command can be run through command line or from CA too. The reason why many people use cacls.exe instead is because using the "lockpermission table" is for some reason often unreliable, and simply doesn’t work always Another reason people mention why cacls should be used instead, is because there is a risk that the "lockpermission" table applies only the permissions in th...

Ice03: can be ignored. Ice64: when any directory error appears, create a same entry in remove file table If you   do not use Roaming Profiles (Intellisync) and Active Directory group policy to assign/publish to Users, you can ignore this error.  It will have no effect on the environment. Ice99: windows volume – this should be in CAPS Ice104: when lockpermissionex and msilockpermissionex both exists, we need to drop the lockpermissionex table. MsiLockPermissionsEx Table enhances the functionality over LockPermissions Table. With MsiLockPermissionsEx table, users now have the ability to set access permissions on objects impacted by the application install that previously required using custom actions or other methods outside of Windows Installer Ice38: we have to make one of hkcu entry (which should not be a file, as key path). ERROR: Component DesktopFolder installs to user profile. It must use a registry key under HKCU as its KeyPath, not a file...