nimrodel
Members-
Posts
49 -
Joined
-
Last visited
Reputation
15 GoodAbout nimrodel

Personal Information
-
Occupation
IT Technician
-
Location
Leicester
-
I've gone 2 days now without a problem, but I'm off at lunchtime until Monday so if it's going to happen again then it'll happen 5 minutes after I leave! I haven't enabled the script yet as I would like to try to fix it without doing that because it is possible that the script could clear the queue just as someone has sent a long job to the printer. However, that option will be put into action on Monday if there have been any blockages before then! I've disabled SNMP too. Not sure how that will help but certainly worth a try. Thanks all for your advice. - - - Updated - - - Yeah, I find that I can never clear print jobs without stopping and starting the spooler!
-
Thank you Sted, I'll give that a go! :-)
-
Hi Steve, Thanks I'll give that a go! The drivers are the specific ones from KM for the printer, but I'll try the workaround. Cheers Dave
-
Hi Sted, Both of your assumptions are correct. I've come across the Windows 10 PDF print issue before but thought I'd got round it by installing Adobe Reader on all PCs. However, I think you are correct. Could you suggest a script to clear the print queue that a member of staff (non-IT) could use in my absence. They are pushing for me to leave instructions on how to fix the problem when I'm not here, but I'm very reluctant to give admin rights / server access to anyone with little knowledge of what they are doing. Thanks Dave
-
I'm not using any third party printer management; just the facility within Server 2016.
-
Hi, I am having a problem which has been ongoing for months and I just cannot sort it. I am using Print Management on my server (running Server2016). When a client prints, the job is sent to the Print Server and then passed out to the printer (Konica Minolta BizHub454). Occasionally (at least 2 or 3 times a week) I will be informed that the printer is not working. On inspection, there will be a long list of jobs in the print queue with the earliest job "stuck". None of the other jobs will even get to the printer so because of one job, the printer is unusable. The way i am fixing this is to stop the Print Spool service and delete the files in the Windows/system32/spool/printers folder. Then re-starting the print spooler clears the queue and all is working again. Trouble is, I work part time and so if the problem happens when I'm not here, it causes chaos. Anyone any ideas what may be causing this and how to cure it?
-
Yep, that's the one. The only thing I can't understand is why it was only applied to my server very recently as it was released in June 2016. I added "domain computers" group to the "delegation" of all my GPOs and they immediately started working!
-
OK guys, I think I've solved the problem!! Although the answer is weird...I have come across an old article (June 2016) warning of a MS update that breaks GPOs. The symptoms were exactly the same as the ones I was experiencing. IF that update was applied to my server last week (why that should be the case is a mystery!) it would explain why policies that were previously working suddenly stopped working. The update (I guess you all know about this) meant that you needed 'authenticated users' group and/or 'domain computers' group in the "delegation" of the GPO. I wasn't aware of that and the affected GPOs didn't have this. I have now added the delegations and (apart from few problems with folder redirection) it SEEMS to be working. Thanks all for your help and suggestions, and thanks MS for yet again bringing out an update unannounced that breaks things!!! ;-)
-
RSOP when logged in as administrator just shows a basic list of applied policies, but none from my GPOs. But why would it if I'm logged in as administrator? These policies are only applying to certain users, not to admins.
-
Hmmm...RSOP.MSC (run on the client) brings up an error: Unable to generate RSoP data. In logging mode, likely causes are Group Policy has never successfully processed for this computer or user., RSoP logging was never enabled, or data is corrupt. In planning mode, verify that the selected domain controller supports RSoP. Details: Invalid namespace
-
gpresult /r is interesting: Last time group policy was applied: 13/11/2017 10:50:20 (this is when I did gpupdate) Group policy was applied from: (gives correct server name) Domain name: (gives correct domain) Applied Group Policy Objects: Default Domain Policy Printers (Neither of my GPOs are being applied!!) The rest seems fine. So this implied that my GPOs don't exist!!! I have checked them and they have been moved into the domain location and they have a group in then security listing called 'PUPILS' of which the user I am logging in with is a member. I have also run GP modelling and this indicates that the GPs should apply. What else can stop it from applying yet not show up in gpresult nor the logs??
-
Don't think scavenging is turned on (not really sure to be honest). Server is physical. Only one server because only small school and it's difficult enough getting money for a pencil ;-) Already tried gpupdate but have also removed apc from teh domain and rejoined and that didn't make any difference. However, gpupdate does nothing but event log reports that both computer and user GPOs completed successfully. But they haven't.
-
Server can be pinged by name from client Only one server so DC & File server the same. The only error on the server event logs is: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
-
Hi, Can anyone help with the following problem please? I created a GPO for all teachers and another one for all pupils. The policy (amongst other things) redirected the user's folders. I have now created a new shared folder on the Server as I wish to store the users' documents in a different place. I created a folder called "PupilFolder" for the pupils and "StaffFolder" for the teachers. I researched the correct permissions for these folders as I know that getting this wrong can cause problems, so I'm fairly confident that the permissions are fine. I amended the 'PUPI'L GPO to redirect the folders to the new location. I then logged on to a pupil account and watched as the folder for that account was created and all the documents were automatically moved across. I did the same for several accounts and all performed perfectly. I did the same for the 'TEACHER' GPO but did not have the teacher passwords so didn't try testing the accounts. The next day I checked the folder expecting to see a folder for each teacher but there were only about 5 folders (should be around 20). When I investigated, all staff were either not picking up the GPO at all or were still being redirected to the old folder (how can this happen?). When I tried to log on to a pupil account, this no longer worked and again the GPO was ignored or the old folder was being used. I also have a separate GPO for each class that puts a different picture on the desktop. This is not being picked up either. Looking at the system log, I get: "The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one or more of the following: a) Name Resolution failure on the current domain controller b) Active Direction Replication Latency (an account created on another domain controller has not replicated to the current domain controller)." As I only have one Server (running 2016) it rules out option (b) but I don't understand how to fix the error (a). Sorry i've waffled...thanks for reading. Any help gratefully accepted. Dave
-
Leicestershire people - EIS + RM smartcache problems?
nimrodel replied to mats's topic in Internet Related/Filtering/Firewall
Hi Sparkeh, Problem is, we are not using a proxy. Dave
