reno-shinigami

Network sharing seems like too much of a pig for me to bother with. I've packaged up the applications and they're ready to ship out to the workstations. AD has also been altered with the relevent scripts. I fixed the decline bug where it wouldn't appear if the logged on again, also fixed the other Decline bug were it wouldn't log if if ran as a login script. Reno. UPDATE: I've distributed the package accross the network and it appears to work like a charm. The main test will be tomorrow when the students arrive.

My prob is, I only know how to do shell script. Unfortunatly, these don't work on student accounts. How did you do it?

Hi all! First of all, can I just say I' new to this forum so if I tread on any toes, please kindly point me in the right direction. AUP Informant is the closest thing to fitting our needs. We need to display 3 separate AUPs depending one whether they're students, staff, or governors. Telling the difference between accounts is only possible via AD/LDAP because we use the full names. e.g. "Joe Bloggs" for students and "JBloggs" for staff. In light of this, I've set up 3 directories: \\server\sysvol\domain.internal\StaffAUP \\server\sysvol\domain.internal\StudentAUP \\server\sysvol\domain.internal\GovAUP All completely identical except for the policy. Annoyingly, I can only execute them locally and not over the network. I know .NET over smb has known issues, but I kind of assumed, considering the documentation, that this had been ironed out of the coding. Solutions greatly appreciated. Otherwise I'll have to make 3 packages to go out on the pc, and execute it off the C drive. Not ideal, but needs a must seen as staff and students go on almost any workstation. Reno.

Virtualization is good for uptime, but that's not all it's good for. Say for example you're hosting websites and you need two webservers. One IIS, one Apache. Problem is, you can't go and make another server and they both need to be on Port 80, so you obviously couldn't install them on the same server, or could you! Enter virtualization. You can install two virtual machines on to one server. Problem solved. 2 webservers, on one server. This is how I use it at any rate. If, however, you install say 5 2k3 servers onto one server, all for AD linked together on the same domain, then you're just wasting power. Reno.