I currently have an MXE3500 running and have added the virtualized windows server to our Active Directory domain. I can go to go to computer management --> local users and groups --> administrators group and add users from our Active Directory domain (after logging in with an account within that domain).
If I modify a share, and give the administrators group full control of that share, plus modify the NTFS permissions to allow full control, I am unable to connect via UNC from my personal computer to that share on the MXE3500. Has anybody been able to do one of the following:
Successfully, apply permissions from a windows domain other then "everyone" to folders that exist on the MXE3500 file system
Run the windows instance as a user within my active directory domain, so that I can map a drive to a UNC share on my active directory domain
Any other way of connecting to a fileshare where I can apply permissions to a select group of people, and then make a folder watch on that fileshare.
Thanks for the reply. I noticed there are quite a few issues with trying to UNC map to any share outside of the local MXE3500. I'm also seeing some issues with FTP watches on an EMC NAS, that has been FTP enabled. The problem I'm seeing now is that the watch will only work, if the watch is at the root level. If I add a file path, its accepted as valid when I save the directory watch, but looking at the fa.log its appending the last directory on twice.
So if my watch is looking at FTP Directory Path of: lifelink
The fa.log shows: .../lifelink/lifelink/
the word lifelink is displayed twice, causing an error, stating: "Error checking file size delay"
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.