marlwoodadmin
Members-
Posts
11 -
Joined
-
Last visited
Reputation
5 NeutralAbout marlwoodadmin

Personal Information
-
Occupation
Network Manager
-
Location
Bristol
-
Important information about Software Support
marlwoodadmin replied to TRobinson's topic in Promethean Direct Support
thanks. I'll contact them now. -
That looks a lot like documentation to me...
-
Important information about Software Support
marlwoodadmin replied to TRobinson's topic in Promethean Direct Support
I am totally confused with the appropriate upgrade path for activstudio. I have 55 Promethean IWB on site (no other brand you will be pleased to here) which have been purchased over the last 10 years. As I understand it each board came with a disk with activstudio on it. Now, because some of these boards are nearly ten years old I have a whole collection of different activstudio versions (1.9; 2; 3). I thought that the newest version of the activstudio software could be used regardless of the age (essentially a free upgrade). I've been on PrometheanPlanet and entered the serial numbers on the cd cases for the software to upgrade to activinspire. However even if i use different software serial numbers i keep getting the same new activinspire serial number being emailed to me. Does that mean that there is no point in entering all the serial numbers i have on the cd cases? Can i just download one version of activinspire and deploy it across the network to all the PCs? What licensing evidence do i need to prove that i can use activstudio/activinspire? Will the IWB themselves be evidence? Thanks for your help -
You CAN use single resizable image. But you MUST sysprep the image with the shutdown switch and then upload the the image. works hunky dory then!
-
You need netdom if you are using XP (i think). Could it be that the username format to join the domain is different? On the web console Win7 works like domain\username but xp was just username. Again i think this i correct as now it is set up i rarely have to change anything. We are using mulitiple FOG clients for various bit of the setup. the FOG server is installed as .31; the init.gz is .29; the client on the PC is .32. FOG doesnt seem to care if all these are mismatched. Reason: FOG server .31 was used because it was the newest one when we set it up init.gz .29 was used because the uploads and deployments are quicker than any other version we have tried Client .32 was used to get the PCs to join the domain even if there was a computer account in AD with the same name
-
You dont need netdom anymore just have the newest fog client on the PC .32. You will need to update the hostnamechanger.dll. C# needs to be .net2 then you create it.
-
You can use the one that ChrisMiles posted at the beginning of this thread.
-
Windows activation could be a problem if a machine is syspreped multiple time. See: Sysprep SkipRearm = 1 Setting skiprearm is the solution for KMS activation (this is done in the unattend.xml)
-
Super. One less thing to do. I will start trying that this week and fingers crossed it should run smoothly. Thats brave of you doing documentation... I always mean to but never get around to it.
-
Thanks for being so active on the forum ChrisMiles. Its been a great help reading your advice. Thanks to you i've got FOG working just fine on windows 7. now i am going to try imaging to muliple machines. Before i do though i was wondering what steps you do to get the drivers on the new image and how this relates to sysprep audit mode. If i have it clear i need to: Install windows 7. Boot into Audit mode. Install all drivers and software for that machine type. sysprep /shutdown upload the image to the Fog server. deploy the image to a new machine type. install/update any drivers sysprep /shutdown upload the image to the Fog server. and on and on it goes until all pcs are in that one image. Do i have to enter audit mode each time i deploy to a new pc type so i can add the drivers, or is this only needed first time around?
-
So can you use the single parttion (resizeable) with windows 7? i swear i tried that before and it didn't work, or does it now work with a new version of FOG. we are running 0.27 if that makes any difference.
