Zum Inhalt

Marco Di Feo Posts

Active Directory time based group membership and LDAP_MATCHING_RULE_IN_CHAIN bug – Update 27.04.23

Microsoft introduced a new feature back in 2016 called „time based group membership“ . Since then it is possible to add groupmembership with an expiration date. There are plenty of examples on how to add a ttl to a groupmembership. I will only explain the basic mechanism on how to determine if a membership is time based or not. After adding a time based membership you can check the groupmemberships with powershell by adding a ShowMemberTimeToLive parameter like this: (Get-ADGroup -LDAPFilter „(CN=ROL-TEST-DIFEO)“ -Properties member -ShowMemberTimeToLive).member The Result of the member field is mixed with normal memberships and time based memberships. Time based memberships have the distinguishedname in the members field with an TTL prefix and look like this <TTL=xxx>,cn=difeo,ou=users… while xxx is time in seconds that this object remains in this group. These seconds count down to 0. After this, the object isnt member of this group anymore. For flexibility we put groups into groups to summarize permissions to roles and not to persons. So it usual that a user has 3 groupmemberships with tons of groups with additional permissions. We cascade groups only one level to keep complexity under contol. So my user difeo is in a group calles…

Powershell CmdLet Set-Printer fails with 0x80070709

We are running several Powershell scripts at our server to add printer remotly at the printserver. From time to time we see the error 0x80070709 with something like „unknown server“. We traced this problem, after we see that some printers fail to get created while some successfully got created at the printserver. So there wasn’t a general problem regarding our server, it had something to do with the set-printer powershell call. After some investigation we found out, that only printers that start(!) with a lowercase character are failing to create. If we change the first char to uppercase, the printers got created without any problem. So maybe someone will help this. I don’t know why or where this happens, but it does and is reproducable

Word / Excel Problem: There is not enough memory or disk space to run word

If you get this annoying message from your favorite MS application, you may have read the internet to the end until you got here. We had the same issue with Word or Excel and tried to get into that problem. First of all, we recognized that it only appears when we upgrade our clients from Windows 7 to Windows 10 1809. If we made a different step between, that everything worked as expected. You may read a lot of stories where Microsoft has a bug on 1809 and you should upgrade to the next Windows 10 version (1903) to „fix“ this problem, but in some cases you can’t and have to deal with this problem like we did. What’s the problem? As you can read in the internet, you may have already mentioned that this issue is a issue with fonts. Some problems occur, when you add fonts to the fonts directory and add an entry to the registry, like everyone does, when you have to deal with additional fonts like barcode fonts e.g. Even it is not recommended, it worked for a long time What did you do while analyzing the root cause? We tried several tools like „fontreg“…