User Profile
hasanemresatilmis
MCT
Joined 6 years ago
User Widgets
Recent Discussions
Re: Bug: Invoke-MgGraphRequest not respecting ErrorAction.
Have you tried the Try-Catch method? For example: try { Invoke-MgGraphRequest -Uri "https://graph.microsoft.com/beta/users/email address removed for privacy reasons" ` -Method GET ` -ErrorAction SilentlyContinue Write-Host "Request continued" } catch { Write-Host "Caught exception: $_" }Re: Deploying Multiple NPS Servers
Even though your CA is AD-integrated and auto-enrollment works, DC2 must explicitly trust the issuing CA and have access to the full certificate chain. Here's what to check: DC2 must have the CA certificate in its Trusted Root Certification Authorities store Open certlm.msc on DC2. Navigate to Trusted Root Certification Authorities > Certificates. Ensure your internal CA certificate is present. If missing, export it from DC1 and import it manually. DC2 must have the Intermediate CA (if applicable) If your CA uses an intermediate certificate, make sure DC2 has it in Intermediate Certification Authorities. DC2 must have a valid server certificate for EAP-TLS NPS uses a server certificate to identify itself during the TLS handshake. Confirm that DC2 has a certificate with: Server Authentication EKU Subject Name or SAN matching the server's name Issued by your internal CA You can use auto-enrollment or manually request it via MMC > Certificates (Computer) > Personal > Request New Certificate. Check NPS Policy Conditions Even if you exported the NPS config, double-check: Connection Request Policies and Network Policies on DC2. Ensure the NAS IP Address or NAS Identifier conditions match what the Cisco AP sends. If DC1 had a policy scoped to its own IP or hostname, DC2 might be rejecting requests. Test with NPS Logging Enable logging on DC2: Open NPS console > Accounting > Log File Properties Enable Log authentication requests Check logs under %SystemRoot%\System32\LogFiles This will show whether DC2 is receiving requests and why it's rejecting them.Re: Demoting DC Windows Server 2019
Active Directory stores the DNS servers hosting a zone in the msDNS-ServerName attribute of the dnsZone object. If XYDC01 is the last registered server for this zone, you’ll receive a warning during demotion. Even if the zone physically exists on other DCs, you’ll encounter this error if it’s not reflected in the metadata. To check which servers are hosting the zone on XYDC01, run: Get-DnsServerZone -Name "enterpriseregistration.jens.be" | Select-Object -ExpandProperty ZoneType Alternatively, use ADSI Edit and navigate to: CN=MicrosoftDNS,DC=ForestDnsZones,DC=jens,DC=be If the msDNS-ServerName attribute of the enterpriseregistration.jens.be object only lists XYDC01, it means the other DCs are not visible in the metadata. Make the zone visible on other DCs On a DC other than XYDC01, remove and re-add the zone to refresh the metadata: Remove-DnsServerZone -Name "enterpriseregistration.jens.be" Add-DnsServerPrimaryZone -Name "enterpriseregistration.jens.be" -ReplicationScope Forest This does not recreate the zone. It simply updates the metadata, since the zone is Active Directory-integrated.Re: Allow “Edit/Save/Rename Without Delete” NTFS Permission
There is no direct NTFS permission available to fully solve this issue. However, to reduce the risk of file deletion while still allowing editing and saving, the following alternative configuration can be applied: Block File Deletion at the Folder Level Grant users Modify permission on the files. Explicitly deny the Delete and Delete Subfolders and Files permissions on the folder. Test application compatibility, especially with programs like Office or AutoCAD that temporarily delete and recreate files during save operations. This configuration allows users to edit files while preventing deletion within the folder. However, some applications may still encounter errors if they rely on temporary file deletion during saving. Related Link: How can I set permission to the user Can edit or rename the file but not allow to delete in Windows file Server 2016? - Microsoft Q&A
