User Profile
lthibx
Brass Contributor
Joined 3 years ago
User Widgets
Recent Discussions
Re: Windows Server 2025 DC Won't Install / Uninstall MSI packages, NIC Domain Category issue.
Yea, though it is a different mix of products, seems that the commonality is the Delayed start setting. Hope MS is monitoring these types of threads and acknowledges that there is a problem.1.3KViews0likes1CommentRe: Windows Server 2025 DC Won't Install / Uninstall MSI packages, NIC Domain Category issue.
Replying to my own post as I have a resolution to the issue. Actually have to give credit to Ninja support. They provided a reference to a Reddit post that had the solution. Being that Ninja also installs Splashtop, the issue reported in other posts, although related to Syncro & Atera applies to Ninja as well as they all use Splashtop (although Ninja has their own Remote app that is awesome, haven't used Splashtop since starting using their remote app)...but I digress. Setting the Splashtop Remote Service to either Disabled or Automatic (Delayed) and rebooting the machine resolves the issue. .MSI packages will now install / uninstall normally. Also, while the issue with the machine's NIC network category automatically being set to Public upon reboot still remains, running the script mentioned before now executes correctly in Task Scheduler. So the Splashtop issue also affected the scheduled task. References: Primary post that helped resolved the issue: https://www.reddit.com/r/syncro/comments/1j26412/splashtop_appears_to_break_windows_server_2025/ Others: https://www.reddit.com/r/WindowsServer/comments/1j261uc/splashtop_win_server_2025_dc/ https://learn.microsoft.com/en-us/answers/questions/2191037/agents-not-communication-after-promoting-a-server?forum=windowserver-all&referrer=answers&page=1#answers https://www.reddit.com/r/WindowsServer/comments/1iq9b4f/applications_wont_install_2025/3.1KViews0likes0CommentsWindows Server 2025 DC Won't Install / Uninstall MSI packages, NIC Domain Category issue.
In the last week I have set up a Win 2025 Server Std Hyper-V host with 2 VMs, one being a domain controller. I have discovered that once the machine is promoted to a DC I can no longer install any .msi packages. .exe packages seem to work fine. My scenario: After setting up the VM (before promotion to DC), I installed my RMM package (.msi - NinjaRMM) and all was fine at that point. I can see and access the VM in my RMM console. After promoting the machine to a DC, I noticed later that the status in my RMM was offline or disconnected. I soon discovered this problem with installing / uninstalling packages. Somehow I was able to uninstall the NinjaRMM, but could not re-install it. Also when Ninja installs the agent it also installs Splashtop. At this point I cannot uninstall Splashtop. Using something simple like the Putty 64bit .msi for testing. Can't install that neither. Any .msi I have tried just hangs for about 30 minutes then times out. Main error code in the .msi log is 1603, which is supposed to be closely related to permissions, but I have found no issues with permissions. Check GPO and have found nothing there either. I have Win 2022 DCs in the same domain and have no issues installing / uninstalling these packages. Internet search has found similar issues, but no answers. Secondly, when rebooting the 2025 DC, the NIC initially gets assigned the Public network category. Disabling / Re-Enabling the adapter the Domain category is immediately assigned. Secondly, I attempted to create a PS script to restart the adapter at startup (task manager...set to run as SYSTEM), and while the tasks starts, it never runs the script. After working with ChatGPT it was suggested to change the script to have a simple one line command 'Exit 0' statment. That doesn't run either. Seems that this problem has relations to being run as SYSTEM, which I believe is also related to the install issue. Internet searches found others stating they have encountered similar issues, but no resolutions. For the install issue, some have stated that if they demote the DC to a member server, .msi installs run successfullly (which seemed to be my case before I promted it a DC). I haven't tried demoting it to a member server, but I did spin up a second Win 2025 Server VM, joined it to the domain and at that point I have no issues installing / uninstalling anything...including .msi packages (oops, I did state this in an earlier paragraph). Tried contacting MS. Seems with no support plan they won't talk with me. That's awesome, you pay for a product, and they won't provide support for it. Such a joy. Hoping that someone might have seen these issues as well. LThibxSolvedRe: Sage 100, 200 on Azure Virtual Desktop Multisession
Bharat Chand At this very moment I am performing the same task...setting up Sage 100 Advanced on AVD. I have both an AVD host and a server running Sage 100 Advanced. I ran into two issues after installing Sage 100 Workstation on the AVD host: First error I received was a Activation Not Found error. I determined it was a permissions issue on the folder where Sage 100 Workstation was installed. Note that as my preference I created a top level folder: C:\Program Files (x86)\Sage, and then installed Sage 100 Workstation there. So it became C:\Program Files (x86)\Sage\Sage 100 Workstation. I had a domain security group for my Sage 100 Users. I set that group with Modify permissions on the C:\Program Files (x86)\Sage folder and those permissions propogated down thru the sublevel files and folders. That resolved the Activation Not Found Issue. Then while in a second AVD session and attempting to access Sage 100 Advance, I received the error "1 User Limit Exceeded. No Valid Activation Found. I found the answer in this Sage KB: https://us-kb.sage.com/portal/app/portlets/results/viewsolution.jsp?solutionid=222924850025520&hypermediatext=null . In summary, I copied the Activation.pvx file from the server to the workstation. After that I was able to access Sage 100 Advance in multiple AVD sessions without error. Did not seem to matter which RDP client I used (though at this date, I either use the Web Client, the Remote Desktop Client, or the new Windows App (all either for Windows or MacOS). Hope this helps with anyone trying to configure AVD & Sage 100. LThibx930Views0likes0CommentsAdminstrators Cannot Log in to Entra ID Joined VMs if Security Defaults are Enabled
Setting up an AVD & File / App Server instance in Azure. Currently working primarily with the File Server VM (fs1) at the moment. FS1 is Entra Id Joined. I can log into the VM with a local administrator or a normal Entra user (non-administrator) without issue. When I attempt to log in with an Entra Admin (global administrator). I get the message "The sign-in method you're trying to use isn't allowed. Try a different sign-in method or contact your system administrator (me)". All users have MFA enabled...actually this is done by Security Defaults being enabled on my Tenant. Not using Conditional Access. Normal users have the Virtual Machine User Login role, and Admins have the Virtual Machine Administrator Login Role. Both are assigned at the Resource Group and inherited by the VM. In the sign-in logs...Activity Details., Normal User Authentication Requirement: Single Factor Authentication. Status: Success...no additional details. Admin User: Authentication Requirement: Multifactor Authentication, Status: Interrupted Additional details: "User needs to perform multi-factor authentication. There could be multiple things requiring multi-factor, e.g. Conditional Access policies, per-user enforcement, requested by client, among others." I have determined that if I disable Security Defaults on my tenant I can then login both as a normal user and Admin user (both Entra users). Trying to figure out a way to get by this without having to have Security Defaults disabled. Seems that the role of Virtual Machine Administrator Login Role, should take care of the Admins. Why are the normal users allowed to bypass MFA but not the Admins? Appreciate the feedback. Lonnie1.2KViews0likes2Comments
Recent Blog Articles
No content to show