-
Posts
632 -
Joined
-
Last visited
Content Type
Forums
News
20th
EduGeek EDIT Conference
Blogs
Everything posted by eean
-
You can do bluescreen for Free in Windows Movie Maker. It's not live though and it is a little fiddly but our year 6 managed it fine last year. This year we're using iMovie 09. As much as I hate to say it, it's a corker of an app.
-
We are just getting frog in - so I'm quite interested in this. When we were buying it I chatted to a technical dude. Apparently, Frog has some kind of SSO system built into it. He said it's up to partners to make their software authenticate against their system, not the other way round - so it depends how standard their SSO system is. Google can authenticate against 'standard' sso systems so I was wondering if it was possible to get Frog to authenticate against it. Now, I know nothing about the system and the next technical dude said 'hmm interesting'. This would be the only way I can think of doing it seamlessly - otherwise you're just going to have to retype your AD username and password, but at least that'd be better than having several passwords. I'm not sure Frog can even accept the NTLM authentication can it? Even if you are logged into windows against AD you still need to log again into Frog.
-
I've never heard of MDT - what is it and how is it better/different to what WDS and Group Policy does anyway? The KB fix I found fixed a problem with Windows XP running sysprep, post image setup from WDS on Server 2008. I think 2008 was the problem - something about requiring enhanced security. Sorry, I assumed that MDT was an add-on for WDS. So this fix might not apply to your problem. I wish I'd found out about MDT before I spent ages getting WDS to work - bloody Microsoft - RIS in legacy mode was so easy, why did the have to take it out of Server 2008?
-
This could be caused by a bug in Windows. I couldn't understand why Sysprep and WDS was not joining the domain. In the end I found applying a KB patch that didn't really relate to the problem fixed it! I'm on holiday now until Tuesday, if you want me to find which KB it was, send me an PM on Wednesday and I'll take a look.
-
Thanks Sherston. Unfortunately my school won't fly me across the world to meet you but I would like to suggest: Proper MSIs to save this messing about. Descriptions in the shortcut of what the program is, so the teacher doesn’t need to open up the software to find out what topics are within it or what it’s about – they can just hover their mouse over the shortcut. Cheers.
-
You know, sometimes I even impress myself! I've just written a little script that will: 1. Run the preliminary MSI, to extract the proper MSI. 2. Run the proper MSI in admin mode to extract a small MSI and all the files within 3. Edit the sherston.ini to change the P: path for saves 4. Create the saves file on the server! 5. Install the file on the local PC so you can test it. Here's what to do: 1. Download AutoitScript and install 2. Open up the editor (now on your start menu) and paste the script in below. 3. Edit the variables at the top to the path of your Resource Pack HD, and to the drive letter of where you want to put the saves files. 4. Create these folders on your c: drive c:\MSIs\Extracted1 and c:\MSIs\Extracted2 5. If you have a q drive mapped, disconnect it temporarily 6. At the cmd prompt type subst q: c:\MSIs\Extracted1 (this will make the computer think that that folder is the q drive). 7. Run the script. You'll need plenty of HD space. After the program has installed you can delete file from Extracted1. 8. Look forward to adding all the MSIs in Extracted 2 to AD. #include #include #Include ;This is the path to the MSI directory on your Sherston hard drive $SourceDir = "E:\RM CC3 Packages\" ;These is where it will find the preliminary install you could make this q:\Applications\ $Extracted1 = "C:\MSIs\Extracted1\Applications\" ;This is where it will place the final MSI $Extracted2 = "C:\MSIs\Extracted2\" ;What drive letter do you want the save path to be? $DriveLetter = "Y" ;This is where the MSIexec file is $msiexec = "c:\windows\system32\msiexec.exe" ;list all the MSI files in the folder $FileList = _FileListToArray($SourceDir, "*.msi", 1) ;Now, for each of those files: For $FileN = 1 to $FileList[0] ;Full Name of the MSI file $CurMSI = $FileList[$FileN] ;Name minus the extension $CurName = StringTrimRight($CurMSI, 4) ;Run the preliminary install ShellExecuteWait($msiexec, " /i " & Chr(34) & $SourceDir & $CurMSI & Chr(34) & " /qb-") ;Run an admin install to extract all the files to 'Extracted2' ShellExecuteWait($msiexec, " /a " & Chr(34) & $Extracted1 & $CurName & "\" & $CurMSI & Chr(34) & " targetdir=" & Chr(34) & $Extracted2 & $CurName & Chr(34) & " /qb-") ;This is the ini file name $IniFile = $Extracted2 & $CurName & "\Sherston.ini" ;Read what the current ini file path is $SavePath = iniread($inifile, "PC", "Savepath", "##ERROR##") ;What is the new path? $NewSavePath = $DriveLetter & StringTrimLeft($SavePath, 1) ;Write the new path IniWrite($inifile, "PC", "Savepath", $NewSavePath) ;Create the new path DirCreate($NewSavePath) ;Run the install so you can test it ShellExecuteWait($msiexec, " /i " & Chr(34) & $Extracted2 & $CurName & "\"& $CurMSI & Chr(34) & " /qb-") Next Note: In 'All Around the House' Sherston didn't hard code the saves path as p: but left it as saves\. My script doesn't recognise that so it needs to be manually set. There are some sherston.ini files that are in a slightly different place, don't use the saves= or are otherwise irregular. Do a search for sherston.ini with error## in the search for text within files box. This will throw up 12 files that need manual editing or deleting. Check within the subfolder for sherston.ini file. Thanks Sherston - this is an excellent resource! EDIT: There are are 16 titles where it will only partly automate this task. This is because sherston have been inconsistent with naming. For these titles you'll need to go c:\msis\extracted1\ and get the name of the msi in the folder. Then run msiexec /a "c:\msis\extracted1\\.msi" targetdir="c:\msis\extracted2\\" /qb- After that you can edit the sherston.ini file in extracted2 Alphonsos Magical Spreadsheet Izzys Story Skills - Goldilocks LDA Prep and Adj Magic Grandad Seaside Holidays Magic Grandad The Great Fire V1.1 Map Detectives Urban Mystery Nature Park ORT Talking Stories Stage 1 & 1+ ORT Talking Stories Stage 2 ORT Talking Stories Stage 3 ORT Talking Stories Stage 6 and 7 ORT Talking Stories Stage 8 and 9 Phoneme Track The Science Express 2 - Life Processes Tizzys Toybox Special Edition. Where in the world is Barnaby Bear I'm sure someone could easily fix my script to automate this though. It's a bit crude but only took me 10 minutes!
-
Download Any Video Converter Free Downloads from a YouTube link and converts to a variety of formats and is the best I've come across.
-
I liked the ipod touches until I found out they don't support flash. Well, that rules out using them with almost every educational app/website that is currently available!
-
2008r2 network/dns issues driving me mad
eean replied to fatnhairy's topic in Windows Server 2008 R2
You've definately got your clients using server 2008 as their only DNS. On the server, the DNS settings on the network card should be 127.0.0.1 (loopback) or it's own IP. Forwarders (within DNS on the server) setup to point to internet dns servers? -
This similar to another question I asked here but phrased a bit more specifically. We have 2 sites (A and B) and 2 domains (New.com and Old.com). Site A: New.com Site B: New.com + Old.com For our transition from old.com to only new.com, we need users to be able to use DCs on either domain. Currently, we have a stub zone setup for new.com on the old.com DC. This allows users using this DNS server to ping new.com DCs, however the computers think they are on Site A not site B. This causes problems with group policy. So, stub zone is wrong. How should I set it up? Can I just set up a primary DNS server for new.com on the old.com DC then enable zone transfers? Thanks!
-
For users you can add Local Printer, TCP/IP Printer, and Shared printer (i.e. \\server\printername) but for computers you can only do Local Printer and TCP/IP printer. You used to be able to add a per machine shared printer connection using Server 2003 R2, or via the command line in windows but they seem to have removed it from 2008. A downgrade?
- 35 replies
-
- group policy
- printers
-
(and 2 more)
Tagged with:
-
So, typical school environment, where users could potentially be logging on almost anywhere: we create one GPO for all users with all the printers, then set up per machine rules/exceptions to decide where that printer is applied? You could have a lot of printers. Does it affect performance? Previously, I set up shared printers per machine and had pushprinterconnections install them. I'm guessing that isn't an option in 2008. Do you know why they let you have IP printers per machine but not shared printers?
- 35 replies
-
- group policy
- printers
-
(and 2 more)
Tagged with:
-
Windows XP, Server 2008 WDS. I have: 1. Setup my base image (it's 100% clean, no drivers, no software) 2. sysprep -mini -reseal -reboot 3. Captured image and added drivers to $OEM$ folders and setup Sysprep.inf correctly on the server. 4. Deplyed image (on same computer). Image deploys fine, it copies the Drivers folder from the server onto the local hard drive and sysprep.inf changes the admin password etc... but the driver install fails (no error message, they just don't install). Sysprep is not updating HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath with the paths OemPnpDriversPath. I've tried MS Workround. The wierd bit: If I manually add the drivers folder and sysprep.inf then run sysprep -mini -reseal -reboot then just restart the computer (i.e. don't capture and deploy) drivers install OK. So it must be something that WDS Server is/isn't doing? Thanks!
-
Are you on Windows XP? If so, there is an update that fixed my domain joining headache. Let me know and I'll root it out for you. The base image should not be attached to the domain. You are running sysprep -mini -reseal -reboot before taking the base image snapshot.
-
I think the default font is set in normal.dot (or normal.dotx for 2007). I reckon you'll have to make a new normal template and do a find a replace on your server to distribute it to all the users profiles.
-
Avery do a couple of different types of tough label so you can print your own using a barcode font (you can download one for free). I think we had a metal-type one.
-
I'd second that. Primary schools are generally screaming out for people to help. You might start with mundane tasks (fixing printers...argh!) but if you're good then they'll see that you're useful. You might also like to offer to help in the classroom i.e. during IT lessons. This way you'll learn the sorts of problems the teachers are having and one day you'll impress them by customising Word to take away all the difficult options, or something. When I was in year 11, I was already getting paid to fix computers and had a job at my own school helping with lessons for the primary children. The next year I was working during my holidays as an IT technician at the school - but I had to 'be in the right place at the right time' doing lots of work for free before I got there! I'm not a technician now, a teacher, but the experience I gained is something you can’t learn on any course - interviewers notice it and comment upon it.
-
Yes. For some reason the zip doesn't work though so I've pasted the 2 files into the post.
-
We went for normal digital cameras. The new basic panasonic now has sound playback and a lithium ion battery, which is much better than faffing with AAs. Will be a little bit over budget. Sound isn't amazing but the video quality is very good.
-
Yes. There are plenty of guides in the webnet teaching you how. It's best to install the printer on the server, share it and get the clients to connect to the server (rather than printing direct via IP). This will remove any driver issues. You may like to have a look at this thread. It has a script I wrote to set the default printer per machine and via active directory.
-
Well, if it works then you don't have a problem! Try hitting F5 a few times when you go to the printer window. The reason is (and why my script has to set the default printer using the registry rather than the default printer command) is that when when you add printers on a per machine basis (like via pushprinterconnections) it takes a good 30-60seconds before they appear in the printers folder. Also check Hkey Current User\Software\Microsoft\Windows NT\CurrentVersion\Windows\ then Device in the registry you should get something like: \\highschool\Media Lab - RISO,winspool,Ne04: Can you tell me what you get. Also, it might not like Media Lab - RISO. Just for testing try making it a one word share name.
-
Printers should always have a static address, regardless of if they are wireless or not. This should be in a range of addresses that is not given out by DHCP. It's best to setup the printer on the server then share the printer. Computers connect to the server printer share and not the printer directly. The server can then queue the prints properly - useful when all the children hit print at once. Although the printer can do this itself, it's better when the server does it (no real limit on memory means that the client machine can be clear of the print quickly). Also, the driver will get pulled down automatically from the server and you set up the default page sizes etc... on the server and it will apply to all users automatically. Should you want to change the IP, again, you'd just do it once on the server. Here's why Microsoft say it's a good idea
-
You could run it inside a virtual server. Then it would be running in it's native operating system. Pretty yucky though.
-
I think I have what you're looking for: I use a free program called CCLogon, which was written by Crash Course Software. It is no longer available for download from their website. You might be able to get them to email it to you ask. Alternatively, PM me and I can send you my MSI package for it. You'll have to edit this MSI, however, for your domain settings. It sits infront of the windows logon and provides a customisable logon interface. I've set it up so the colours and logos make it look like the standard non-domain logon. Each year group has it's own domain logon with no password, the kids click on their year name and then click logon - easy. Older children and staff can access the standard logon by holding shift and clicking. It has one bug: When windows update installs updates that require a restart, it prevents the computer from restarting itself. When people try to logon it says 'wrong password'. It's rarely a problem. People just need to know to restart or use shift click (whereupon the computer will restart anyway). I think it will only work with XP.
