-
Posts
31 -
Joined
-
Last visited
Reputation
5 NeutralAbout danmoly

Personal Information
-
Occupation
IT Technician
-
Location
United Kingdom
-
Have you tried location blocking of .exe's? That what we have deployed. In Group policy there are Software Restriction Polices, and we've specified everything to block, but allowed via Paths specified. So allow %PROGRAMFILES% etc. and then restrict read/write to the C: so students and staff alike cannot access, write and run their own executable's. So when they chuck in a USB as we havn't specified the path nothing can run from there. Likewise if they copy it to their user spaces.
-
So the culprit was the WMA file types! MP3's burn fine, very odd. Thanks for all the help as ever guys. Shame it wasn't anything more exciting then file types!??!
- 11 replies
-
- audio
- group policy
-
(and 1 more)
Tagged with:
-
Funnily enough you might be right. I assumed I would be able to burn them, as I've done so in the past. But no it won't do it, on my own machine and test PC. The files are WMA's which should be supported. I'm just in the process of converting them to MP3 now, see if that helps at all.
- 11 replies
-
- audio
- group policy
-
(and 1 more)
Tagged with:
-
- 11 replies
-
- audio
- group policy
-
(and 1 more)
Tagged with:
-
So I've tried this, gave user permissions to the temp folder which is something like "%USERNAME%\Appdata\Local\Microsoft\Windows\Burn\Burn" and no luck? Maybe because its a variable? In the test environment I did give full permission to the C: ?! We don't have the libraries disabled, so that shouldn't be the issue?
- 11 replies
-
- audio
- group policy
-
(and 1 more)
Tagged with:
-
so just took of the restriction in a quick test environment, and it still errors??? Any clues to why this is happening?
- 11 replies
-
- audio
- group policy
-
(and 1 more)
Tagged with:
-
Not tried that yet, will do and get back to you. I would say we would do the same but here I feel the staff would do more damage then the students to the C drive!
- 11 replies
-
- audio
- group policy
-
(and 1 more)
Tagged with:
-
Hello all, So had a request form a staff member trying to burn an audio CD, claiming it errors. Me thinking it was a user error it seems they were correct. Looks like due to our C drive restriction, the audio files get put into a temporary user folder before the burn. Anyone else had to deal with this? or am I wrong in the error? I've tried adding in permissions to the folders but doesn't seem to work for the roaming users. Thanks, Dan
- 11 replies
-
- audio
- group policy
-
(and 1 more)
Tagged with:
-
Good morning all, So I am at my wits end with a certain user and our Digital Signage. I very painstakingly set up 3 screens last summer, one in particular for our Canteen (which was requested). Now its taken some time to show and guide the user how to update the screen with new menus each day. Now they've finally cracked it, they are ruining it... clip art, font changes, colour schemes, its just hideous. The way I've got it setup is I've designed a background applied to a publisher doc, and formatted all the necessary boxes with the right looking fonts, colour etc. The problem is, the user can edit this, which is fine, that's the point, but i only want them to edit the text, not the aesthetics of the thing, especially adding in clipart and horrible snippets form the web. So my question is does anyone know how to restrict editing on a publisher file? I see it can be done in Word, but need it to be in Publisher really, unless someone has a way of exporting a Word doc to an image file that's not PDF...? (requirements of the digital signage, need jpeg/png etc.) Apologies for the rant, it just frustrates me, the hard work one parts into something, getting it all working and looking nice, for someone to come along and effectively poop on it... Thanks, dan
-
WSUS - Clients not yet reported (not syncing the updates)
danmoly replied to danmoly's topic in Windows Server 2008 R2
Just an update. Its now working. Went through a load of troubleshooting this morning again, and decided to restart the server. it did two little updates in the process, but now all is well! Maybe as I hadn't restarted from the first install or something in the update fixed it, whichever I don't mind now its working! Thanks again for everyones help! very much appreciated. -
WSUS - Clients not yet reported (not syncing the updates)
danmoly replied to danmoly's topic in Windows Server 2008 R2
Gave it a go, disabled firewall on both the wsus server and the client still nothing?! -
WSUS - Clients not yet reported (not syncing the updates)
danmoly replied to danmoly's topic in Windows Server 2008 R2
what would the firewall settings be? Theres no obviously options to add WSUS or similar into it. -
WSUS - Clients not yet reported (not syncing the updates)
danmoly replied to danmoly's topic in Windows Server 2008 R2
Right so, the VM WSUS server (Win 2008r2) needs proxy details in to get internet access. It then has the proxy details entered in the WSUS options (which run on :8080). GPO side of things I've entered the server name http://HTTP://SERVERNAME with and without :80 (as it is WSUS v3.2...) and the IP of the server. All to no avail. Still the same error when trying to run on the client, after performing a gpupdate and wuauclt. Oh and wsus server name is in the internet exceptions list. Thanks for all the help so far. I'm sure its something silly somewhere, but for the life of me can't figure it out. -
WSUS - Clients not yet reported (not syncing the updates)
danmoly replied to danmoly's topic in Windows Server 2008 R2
Am i running this on the client? doesn't seem to do anything? -
WSUS - Clients not yet reported (not syncing the updates)
danmoly replied to danmoly's topic in Windows Server 2008 R2
Okay so added it into exceptions and still nothing. Can I clarify some things. This may sound dumb but this is my first WSUS server... So WSUS, does the server itself need the proxy settings entered? As in on the internet options? And in the WSUS options I've entered the proxy info in there as the guide suggested, and this runs over port 8080, so on the GPO side would the server address be *:80 or :8080? Also, another dumb question perhaps, but I'm currently testing it if its working but manually going into Windows Update on the client machine and hitting update? Should this still work when using a WSUS? Thanks,
