theeggmaster Posted March 18, 2019 Posted March 18, 2019 I'm currently helping another Secondary school out with their IT. They run an RM CC4 network (which is something I don't have much experience in), but I'm coming up with a Sibelius issue on Windows 7. A small number of students are getting a prompt for an Admin username and password when they try to run Sibelius. However, it's not down to the machine as other students can log onto the same machine and get Sibelius running. I can also run it successfully as an admin. Anyone got any ideas on how to fix this?
jthompson Posted March 18, 2019 Posted March 18, 2019 Perhaps try clearing the affected students' profiles of the affected machine(s) first. Sibelius may need to be launched as an admin before it's happy with subsequent use by other users: the affected users' first usage may have preceded any use by an admin.
theeggmaster Posted March 18, 2019 Author Posted March 18, 2019 Unfortunately, when I look in the User Profiles section to delete them, their accounts are not appearing (there are lots of strange things happening on this network). I've tried resetting their profile in RM, but this doesn't fix the issue.
BOOT Posted March 19, 2019 Posted March 19, 2019 Try changing the [Everyone] or [users] permissions on [%SYSTEMDRIVE%\ProgramData\Avid] to [Modify]? 1
theeggmaster Posted March 19, 2019 Author Posted March 19, 2019 Try changing the [Everyone] or [users] permissions on [%SYSTEMDRIVE%\ProgramData\Avid] to [Modify]? I'll certainly give that a go later this week.
OverWorked Posted July 10, 2019 Posted July 10, 2019 You've probably fixed this by now, but Sibelius does this if when it searches for the license server on the first run after installation. For me, I just ran Sibelius once as local admin, then let it find the license server. It's OK after that.
theeggmaster Posted July 10, 2019 Author Posted July 10, 2019 Actually, it turned out that the way the software was installed was with individual licences, rather than the team at the time setting up the license server, so when machines were rebuilt, they didn't have the licence key on and tried to contact the licence server, hence the admin prompty. Eventually I found the individual licences and put those on each machine.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now