• ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
The HP Community is where owners of HP products, like you, volunteer to help each other find solutions.
Archived This topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.

‎03-22-2017 06:18 AM

HP Recommended
Product: M553
Operating System: Other

 

Tried this via LDAP and Windows login service with no luck.  This is a MS domain network with two trial groups setup, one global and one universal in scope, just to test all possibilities.  

 

My original test group had a space in it, so I created another to see if the spaces caused any issues with this.

 

If I restricted a USER with the Windows sign in method, all works exactly as expected.  The format used for the Network User field would be formatted as such:  DOMAIN\user

 

Just when I switch it to GROUP instead of user, the expected behavior stops functioning.

 

Confirmed several times over the same user successfully tested with the USER control belongs in the groups tested.

 

I have nearly tested every possible permutation of group formatting in the Group/Network User field.  Some of the formats tested include and are not limited to:

 

DOMAIN\group

DOMAIN\group\

\group

\group\

CN=group,OU=ouname,OU=ouname,DC=domain,DC=Local

DOMAIN.local/ouname/ouname/group

DOMAIN.local\ouname\ouname\group

 

I've also tried these in ' ' and " " when the naming conventions include spaces.

 

Is there a fault when a group has a space or is nested within an OU with a space?  This is truly my only hunch at this point as to why it's not functioning as it should when trying to grant access by Group.

 

 

As a side note, these groups/structures/memberships have existed for days, so it isn't some logical replication/ldap querying cycle delay

 

Thank you

Archived This topic has been archived. Information and links in this thread may no longer be available or relevant. If you have a question create a new topic by clicking here and select the appropriate board.
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.

Didn't find what you were looking for? Ask the community

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.