EV Deployment Scanner reporting on removed FSA Volume
We going to be upgrading EV (Two Steps, 8.0.4 to 9.0.5 and 9.0.5 to 10.0.4 R1 + CHF2) and we're running the Deployment scanner to see what needs cleaned up prior to the work.
Most of the error's/warnings have been cleared but there are a number of issues relating to "File Share Permissions".
We used to create a volume for each file server drive (e.g E$ or K$) prior to creating the actual volume and subsequent Folder archive point to allow some scripted operations used by our server team. We've now removed the need for these drive volume points and as they don't actually archive anything we'll be removing them.
Deployment scanner however is reporting "Enterprise Vault Deployment Scanner is unable to determine whether or not the user CLD1\evaccount has read\write permissions to the share \\file_server\e$. Please verify that the user has read\write permissions to \\file_server\e$ before adding it as a File Server Archiving target."
We've removed e$ as a volume point within EV for the file server in question yet it's still reporting on it within Deployment Scanner.
I've rebooted the environment since making the change but this hasn't cleared it up.
I know Deployment scanner populates the "File Shares" config before running so why would it still be reporting on a volume which is no longer configured ?
It's not a major problem as we don't archive anything under the likes of e$ directly anyway but I'd like to clear it up before the upgrade anyway.