Knowledge Partner
Knowledge Partner
826 views

Changing home directory in AD - filr sees no changes

Is this normal or a bug?

Filr Version: 2.0.0.421-HP.492

AD users have their home dir populated and Filr does see the Net Folder server.

Changed a users Home Dir setting in AD to a *NEW* file server that Filr does not yet know about.
Waited a half an hour.

Ran a manual Sync All.


Filr sees other user accounts added/deleted/modified, but not the one I changed.
New NetFolder server does NOT show up.

The only way I could get Filr to see the change was to delete the user out of Filr and re-run the sync, so that it added the user and then the New NetFolder shows up for configuration.

Is this normal?

I would've thought it would see the home directory attribute as a "modified"?
0 Likes
10 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Changing home directory in AD - filr sees no changes

On 08/29/2017 03:54 PM, kjhurni wrote:
>
> Is this normal or a bug?


AFAIR the home directory attribute in the Filr data base will be updated
the next time the user logs in.

Günther

0 Likes
Knowledge Partner
Knowledge Partner

Re: Changing home directory in AD - filr sees no changes

On Tue, 29 Aug 2017 13:54:02 GMT, kjhurni
<kjhurni@no-mx.forums.microfocus.com> wrote:

>
>Is this normal or a bug?
>
>Filr Version: 2.0.0.421-HP.492
>
>AD users have their home dir populated and Filr does see the Net Folder
>server.
>
>Changed a users Home Dir setting in AD to a *NEW* file server that Filr
>does not yet know about.
>Waited a half an hour.
>
>Ran a manual Sync All.
>
>
>Filr sees other user accounts added/deleted/modified, but not the one I
>changed.
>New NetFolder server does NOT show up.
>
>The only way I could get Filr to see the change was to delete the user
>out of Filr and re-run the sync, so that it added the user and then the
>New NetFolder shows up for configuration.
>
>Is this normal?
>
>I would've thought it would see the home directory attribute as a
>"modified"?


I'm not sure why this doesn't get picked up. I should look into it,
but haven't had time. Last time I had a home folder change, I
directly modified the Filr accounts for the affected users. It was
only a dozen people so not a big deal.

--
Ken
Knowledge Partner

If this post was helpful and you are logged into the web interface,
please show your appreciation and click on the star below... Thanks!

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html
--
Ken
Knowledge Partner

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html
0 Likes
Knowledge Partner
Knowledge Partner

Re: Changing home directory in AD - filr sees no changes

=?UTF-8?Q?G=c3=bcnther_Schwarz?=;2465124 wrote:
On 08/29/2017 03:54 PM, kjhurni wrote:
>
> Is this normal or a bug?


AFAIR the home directory attribute in the Filr data base will be updated
the next time the user logs in.

Günther


Nope. Tried that.

Normally what happens is this:
1) You have to setup an LDAP repository, then run the Sync. This will look for the Home Dir attribute. If something (or multiple somethings are found) it'll populate the Net Folder Server with new servers (with yellow exclamation points). But it still finds/sees the servers.

2) Until the user logs into the Filr, the Filr "Profile" will show no Home Directory.

The issue seems to be that a user that has a home dir attribute in Filr (via LDAP sync) AND has logged in, if that home dir attribute CHANGES, the Filr server will not create a new Net Folder server, and thus, the use will login and see a big fat nothing in their My Files at that point.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Changing home directory in AD - filr sees no changes

On Tue, 29 Aug 2017 16:24:02 GMT, kjhurni
<kjhurni@no-mx.forums.microfocus.com> wrote:

>
>=?UTF-8?Q?G=c3=bcnther_Schwarz?=;2465124 Wrote:
>> On 08/29/2017 03:54 PM, kjhurni wrote:
>> >
>> > Is this normal or a bug?

>>
>> AFAIR the home directory attribute in the Filr data base will be
>> updated
>> the next time the user logs in.
>>
>> Günther

>
>Nope. Tried that.
>
>Normally what happens is this:
>1) You have to setup an LDAP repository, then run the Sync. This will
>look for the Home Dir attribute. If something (or multiple somethings
>are found) it'll populate the Net Folder Server with new servers (with
>yellow exclamation points). But it still finds/sees the servers.
>
>2) Until the user logs into the Filr, the Filr "Profile" will show no
>Home Directory.
>
>The issue seems to be that a user that has a home dir attribute in Filr
>(via LDAP sync) AND has logged in, if that home dir attribute CHANGES,
>the Filr server will not create a new Net Folder server, and thus, the
>use will login and see a big fat nothing in their My Files at that
>point.


I was just online with Tech Support about a Filr related issue and
asked about this. I was told the way it is supposed to work is that
when the user logs into Filr, if a sync has taken place, the home
folder should be updated to match the updated home folder from the
directory. I tested it here (I'm running eDirectory) and found the
following:

1. Changed userA home folder in eDirectory.
2. Ran an ldap sync in Filr (oddly, nothing was listed as changed).
3. Logged in as userA, received an error that folder was inaccessible.
4. Ran another ldap sync in Filr (again, nothing listed as changed).
5. Logged in as userA, home folder was correct and accessible.

I'm not sure if it took 2 ldap syncs or 2 logins by the user or if I
just logged in too quickly. But it does seem to be working. Not sure
why the ldap sync made no mention of the user home folder change. If
you aren't seeing similar results, you may want to open an SR.

--
Ken
Knowledge Partner

If this post was helpful and you are logged into the web interface,
please show your appreciation and click on the star below... Thanks!

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html
--
Ken
Knowledge Partner

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html
0 Likes
Knowledge Partner
Knowledge Partner

Re: Changing home directory in AD - filr sees no changes

ketter;2465154 wrote:
On Tue, 29 Aug 2017 16:24:02 GMT, kjhurni
<kjhurni@no-mx.forums.microfocus.com> wrote:

>
>=?UTF-8?Q?G=c3=bcnther_Schwarz?=;2465124 Wrote:
>> On 08/29/2017 03:54 PM, kjhurni wrote:
>> >
>> > Is this normal or a bug?

>>
>> AFAIR the home directory attribute in the Filr data base will be
>> updated
>> the next time the user logs in.
>>
>> Günther

>
>Nope. Tried that.
>
>Normally what happens is this:
>1) You have to setup an LDAP repository, then run the Sync. This will
>look for the Home Dir attribute. If something (or multiple somethings
>are found) it'll populate the Net Folder Server with new servers (with
>yellow exclamation points). But it still finds/sees the servers.
>
>2) Until the user logs into the Filr, the Filr "Profile" will show no
>Home Directory.
>
>The issue seems to be that a user that has a home dir attribute in Filr
>(via LDAP sync) AND has logged in, if that home dir attribute CHANGES,
>the Filr server will not create a new Net Folder server, and thus, the
>use will login and see a big fat nothing in their My Files at that
>point.


I was just online with Tech Support about a Filr related issue and
asked about this. I was told the way it is supposed to work is that
when the user logs into Filr, if a sync has taken place, the home
folder should be updated to match the updated home folder from the
directory. I tested it here (I'm running eDirectory) and found the
following:

1. Changed userA home folder in eDirectory.
2. Ran an ldap sync in Filr (oddly, nothing was listed as changed).
3. Logged in as userA, received an error that folder was inaccessible.
4. Ran another ldap sync in Filr (again, nothing listed as changed).
5. Logged in as userA, home folder was correct and accessible.

I'm not sure if it took 2 ldap syncs or 2 logins by the user or if I
just logged in too quickly. But it does seem to be working. Not sure
why the ldap sync made no mention of the user home folder change. If
you aren't seeing similar results, you may want to open an SR.

--
Ken
Knowledge Partner

If this post was helpful and you are logged into the web interface,
please show your appreciation and click on the star below... Thanks!

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html


So what's interesting is that yours varies a little from mine.

What I did (and duped numerous times):
1) User logs into filr and has Home Folder attribute (in Filr) set to: \\oldserver\volume
2) Filr only has ONE Net Folder Server in the list: oldserver
3) Go into AD, and modify that users home directory attribute in AD to point to NEW server.
4) Run Filr LDAP Sync. Filr does NOT see change and does NOT auto-create/import the NEW Net Folder Server
5) Login to Filr as that user. User sees "old" stuff. Go back into Admin Console and check that user. Home Folder profile in Filr still shows old Net Folder Server
6) Filr STILL doesn't show new Net Folder server object.
7) Re-run LDAP Sync. Nothing changes.

Basically until you manually create the NetFolder server in Filr (OR Delete the user from Filr and then re-run LDAP sync), it won't work.

Now, once the Net Folder SERVER object is created in Filr, and you configure it, THEN it appears that any subsequent changes to other users will work as you (and Tech support as I opened an SR) describe.

Tech support seems to be "missing" that the Net Folder server is NOT auto-created as it should be (on a very initial setup, it auto-creates Net Folder Server (s) based upon the LDAP sync).

And of course, without a valid definition, Filr has no idea how to talk to the new server.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Changing home directory in AD - filr sees no changes

On Wed, 30 Aug 2017 15:14:02 GMT, kjhurni
<kjhurni@no-mx.forums.microfocus.com> wrote:

>
>ketter;2465154 Wrote:
>> On Tue, 29 Aug 2017 16:24:02 GMT, kjhurni
>> <kjhurni@no-mx.forums.microfocus.com> wrote:
>>
>> >
>> >=?UTF-8?Q?G=c3=bcnther_Schwarz?=;2465124 Wrote:
>> >> On 08/29/2017 03:54 PM, kjhurni wrote:
>> >> >
>> >> > Is this normal or a bug?
>> >>
>> >> AFAIR the home directory attribute in the Filr data base will be
>> >> updated
>> >> the next time the user logs in.
>> >>
>> >> G?
>> >
>> >Nope. Tried that.
>> >
>> >Normally what happens is this:
>> >1) You have to setup an LDAP repository, then run the Sync. This will
>> >look for the Home Dir attribute. If something (or multiple somethings
>> >are found) it'll populate the Net Folder Server with new servers (with
>> >yellow exclamation points). But it still finds/sees the servers.
>> >
>> >2) Until the user logs into the Filr, the Filr "Profile" will show no
>> >Home Directory.
>> >
>> >The issue seems to be that a user that has a home dir attribute in

>> Filr
>> >(via LDAP sync) AND has logged in, if that home dir attribute CHANGES,
>> >the Filr server will not create a new Net Folder server, and thus, the
>> >use will login and see a big fat nothing in their My Files at that
>> >point.

>>
>> I was just online with Tech Support about a Filr related issue and
>> asked about this. I was told the way it is supposed to work is that
>> when the user logs into Filr, if a sync has taken place, the home
>> folder should be updated to match the updated home folder from the
>> directory. I tested it here (I'm running eDirectory) and found the
>> following:
>>
>> 1. Changed userA home folder in eDirectory.
>> 2. Ran an ldap sync in Filr (oddly, nothing was listed as changed).
>> 3. Logged in as userA, received an error that folder was inaccessible.
>> 4. Ran another ldap sync in Filr (again, nothing listed as changed).
>> 5. Logged in as userA, home folder was correct and accessible.
>>
>> I'm not sure if it took 2 ldap syncs or 2 logins by the user or if I
>> just logged in too quickly. But it does seem to be working. Not sure
>> why the ldap sync made no mention of the user home folder change. If
>> you aren't seeing similar results, you may want to open an SR.
>>
>> --
>> Ken
>> Knowledge Partner
>>
>> If this post was helpful and you are logged into the web interface,
>> please show your appreciation and click on the star below... Thanks!
>>
>> Create and vote for enhancements!
>> https://www.microfocus.com/products/enhancement-request.html

>
>So what's interesting is that yours varies a little from mine.
>
>What I did (and duped numerous times):
>1) User logs into filr and has Home Folder attribute (in Filr) set to:
>\\oldserver\volume
>2) Filr only has ONE Net Folder Server in the list: oldserver
>3) Go into AD, and modify that users home directory attribute in AD to
>point to NEW server.
>4) Run Filr LDAP Sync. Filr does NOT see change and does NOT
>auto-create/import the NEW Net Folder Server
>5) Login to Filr as that user. User sees "old" stuff. Go back into
>Admin Console and check that user. Home Folder profile in Filr still
>shows old Net Folder Server
>6) Filr STILL doesn't show new Net Folder server object.
>7) Re-run LDAP Sync. Nothing changes.
>
>Basically until you manually create the NetFolder server in Filr (OR
>Delete the user from Filr and then re-run LDAP sync), it won't work.
>
>Now, once the Net Folder SERVER object is created in Filr, and you
>configure it, THEN it appears that any subsequent changes to other users
>will work as you (and Tech support as I opened an SR) describe.
>
>Tech support seems to be "missing" that the Net Folder server is NOT
>auto-created as it should be (on a very initial setup, it auto-creates
>Net Folder Server (s) based upon the LDAP sync).
>
>And of course, without a valid definition, Filr has no idea how to talk
>to the new server.


I'm running 3.2, that might be the difference.

--
Ken
Knowledge Partner

If this post was helpful and you are logged into the web interface,
please show your appreciation and click on the star below... Thanks!

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html
--
Ken
Knowledge Partner

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Changing home directory in AD - filr sees no changes

On 08/30/2017 05:14 PM, kjhurni wrote:
> Basically until you manually create the NetFolder server in Filr (OR
> Delete the user from Filr and then re-run LDAP sync), it won't work.
>
> Now, once the Net Folder SERVER object is created in Filr, and you
> configure it, THEN it appears that any subsequent changes to other users
> will work as you (and Tech support as I opened an SR) describe.
>
> Tech support seems to be "missing" that the Net Folder server is NOT
> auto-created as it should be (on a very initial setup, it auto-creates
> Net Folder Server (s) based upon the LDAP sync).


In my environment we have a limited number of OES volumes which contain
home folders. All of these where configured as Net Folder Servers in
Filr upon the initial configuration. So when I move a user's home folder
from one folder to another this works with Filr also. LDAP sync is done
on schedule so I will have to check for the correct order of syncing and
user login. But my guess is that eDirectory is checked for the home
folder attribute as configured in the LDAP sync upon login.

Now if the user's home folder is moved to a volume that is not
configured yet in Filr as a Net Folder Server things will not work
properly as Filr does not know how to access that volume. The
administrator will have to set the server type and the proxy user at
least. In my environment I will get an error message on the Filr
administration web page asking for configuration of the new Net Folder
Server. So the new Net Folder Server is indeed created automatically but
stays in an error state and is thus not accessible for the user.

Günther

0 Likes
Knowledge Partner
Knowledge Partner

Re: Changing home directory in AD - filr sees no changes

=?UTF-8?Q?G=c3=bcnther_Schwarz?=;2465300 wrote:
On 08/30/2017 05:14 PM, kjhurni wrote:
> Basically until you manually create the NetFolder server in Filr (OR
> Delete the user from Filr and then re-run LDAP sync), it won't work.
>
> Now, once the Net Folder SERVER object is created in Filr, and you
> configure it, THEN it appears that any subsequent changes to other users
> will work as you (and Tech support as I opened an SR) describe.
>
> Tech support seems to be "missing" that the Net Folder server is NOT
> auto-created as it should be (on a very initial setup, it auto-creates
> Net Folder Server (s) based upon the LDAP sync).


In my environment we have a limited number of OES volumes which contain
home folders. All of these where configured as Net Folder Servers in
Filr upon the initial configuration. So when I move a user's home folder
from one folder to another this works with Filr also. LDAP sync is done
on schedule so I will have to check for the correct order of syncing and
user login. But my guess is that eDirectory is checked for the home
folder attribute as configured in the LDAP sync upon login.

Now if the user's home folder is moved to a volume that is not
configured yet in Filr as a Net Folder Server things will not work
properly as Filr does not know how to access that volume. The
administrator will have to set the server type and the proxy user at
least. In my environment I will get an error message on the Filr
administration web page asking for configuration of the new Net Folder
Server. So the new Net Folder Server is indeed created automatically but
stays in an error state and is thus not accessible for the user.

Günther


Maybe it only happens with AD then.

All I know is that adding a NEW server UNC path in the AD Home Directory attribute, does not cause Filr LDAP sync to auto-create a new Net Folder Server definition.
At least a fully patched Filr 2.1 system.

Now, once it DOES get created, and the Admin sets it up, then it seems the LDAP sync will properly adjust things for the user objects in its database.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Changing home directory in AD - filr sees no changes

ketter;2465248 wrote:
On Wed, 30 Aug 2017 15:14:02 GMT, kjhurni
<kjhurni@no-mx.forums.microfocus.com> wrote:

>
>ketter;2465154 Wrote:
>> On Tue, 29 Aug 2017 16:24:02 GMT, kjhurni
>> <kjhurni@no-mx.forums.microfocus.com> wrote:
>>
>> >
>> >=?UTF-8?Q?G=c3=bcnther_Schwarz?=;2465124 Wrote:
>> >> On 08/29/2017 03:54 PM, kjhurni wrote:
>> >> >
>> >> > Is this normal or a bug?
>> >>
>> >> AFAIR the home directory attribute in the Filr data base will be
>> >> updated
>> >> the next time the user logs in.
>> >>
>> >> G?
>> >
>> >Nope. Tried that.
>> >
>> >Normally what happens is this:
>> >1) You have to setup an LDAP repository, then run the Sync. This will
>> >look for the Home Dir attribute. If something (or multiple somethings
>> >are found) it'll populate the Net Folder Server with new servers (with
>> >yellow exclamation points). But it still finds/sees the servers.
>> >
>> >2) Until the user logs into the Filr, the Filr "Profile" will show no
>> >Home Directory.
>> >
>> >The issue seems to be that a user that has a home dir attribute in

>> Filr
>> >(via LDAP sync) AND has logged in, if that home dir attribute CHANGES,
>> >the Filr server will not create a new Net Folder server, and thus, the
>> >use will login and see a big fat nothing in their My Files at that
>> >point.

>>
>> I was just online with Tech Support about a Filr related issue and
>> asked about this. I was told the way it is supposed to work is that
>> when the user logs into Filr, if a sync has taken place, the home
>> folder should be updated to match the updated home folder from the
>> directory. I tested it here (I'm running eDirectory) and found the
>> following:
>>
>> 1. Changed userA home folder in eDirectory.
>> 2. Ran an ldap sync in Filr (oddly, nothing was listed as changed).
>> 3. Logged in as userA, received an error that folder was inaccessible.
>> 4. Ran another ldap sync in Filr (again, nothing listed as changed).
>> 5. Logged in as userA, home folder was correct and accessible.
>>
>> I'm not sure if it took 2 ldap syncs or 2 logins by the user or if I
>> just logged in too quickly. But it does seem to be working. Not sure
>> why the ldap sync made no mention of the user home folder change. If
>> you aren't seeing similar results, you may want to open an SR.
>>
>> --
>> Ken
>> Knowledge Partner
>>
>> If this post was helpful and you are logged into the web interface,
>> please show your appreciation and click on the star below... Thanks!
>>
>> Create and vote for enhancements!
>> https://www.microfocus.com/products/enhancement-request.html

>
>So what's interesting is that yours varies a little from mine.
>
>What I did (and duped numerous times):
>1) User logs into filr and has Home Folder attribute (in Filr) set to:
>\\oldserver\volume
>2) Filr only has ONE Net Folder Server in the list: oldserver
>3) Go into AD, and modify that users home directory attribute in AD to
>point to NEW server.
>4) Run Filr LDAP Sync. Filr does NOT see change and does NOT
>auto-create/import the NEW Net Folder Server
>5) Login to Filr as that user. User sees "old" stuff. Go back into
>Admin Console and check that user. Home Folder profile in Filr still
>shows old Net Folder Server
>6) Filr STILL doesn't show new Net Folder server object.
>7) Re-run LDAP Sync. Nothing changes.
>
>Basically until you manually create the NetFolder server in Filr (OR
>Delete the user from Filr and then re-run LDAP sync), it won't work.
>
>Now, once the Net Folder SERVER object is created in Filr, and you
>configure it, THEN it appears that any subsequent changes to other users
>will work as you (and Tech support as I opened an SR) describe.
>
>Tech support seems to be "missing" that the Net Folder server is NOT
>auto-created as it should be (on a very initial setup, it auto-creates
>Net Folder Server (s) based upon the LDAP sync).
>
>And of course, without a valid definition, Filr has no idea how to talk
>to the new server.


I'm running 3.2, that might be the difference.

--
Ken
Knowledge Partner

If this post was helpful and you are logged into the web interface,
please show your appreciation and click on the star below... Thanks!

Create and vote for enhancements!
https://www.microfocus.com/products/enhancement-request.html


Yeah, my testlab Filr 3.x system works fine as well (I haven't touched it for months, so I went in and saw it was waiting for me to configure the new NetFolder server).

So two possiblities I see:
a) Filr 2.0.whatever version I posted has a bug/feature
b) A *manual* Sync All doesn't work, but letting the scheduled sync does (that's the only other difference in my Filr 3.x system is that the manual syncs had never been run for months, just the scheduled nightly ones).
0 Likes
Knowledge Partner
Knowledge Partner

Re: Changing home directory in AD - filr sees no changes

So engineering was able to duplicate. The issue is with the "manual" sync. Doesn't work in 2.x-3.x of Filr (in the sense that if you've "added" a new server to your environment, and modified a user's home directory setting to use that new server, the Filr Sync Now won't auto-create the New NetFolder server).

HOWEVER:
The scheduled sync (ie: leave it alone, and when your *scheduled* sync kicks in, THEN it will auto-create the new NetFolder server) works.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.