Joanne Posted July 15, 2014 Posted July 15, 2014 Here's a head scratcher for you. It's not really a problem, just a bit annoying. I created a Windows 7 image on a Toshiba Satellite Pro C50. I sysprepped, generalized and deploy via WDS. When I deploy the image I get different KMS behaviours off different models of Toshiba laptop. My Satellite Pro C850's activate Windows, but not Office. My Satellite Pro C660's activate Office, but not Windows. I am running the following on an elevated command prompt to activate. Keys are the generic ones off Microsoft... Windows Activation cscript slmgr.vbs /ipk FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4 cscript slmgr.vbs /ato Office Activation cd C:\Program Files (x86)\Microsoft Office\Office15 cscript ospp.vbs /act Any ideas on why this is happening? Drivers perhaps?
Joanne Posted July 15, 2014 Author Posted July 15, 2014 VAMT? Yeah. It activates fine through that, but because they are laptops, it's easier just to activate as I image because I have to tweak little bits anyway.
Joanne Posted July 15, 2014 Author Posted July 15, 2014 Has anyone else ever had any things like this going on?
SHimmer45 Posted July 15, 2014 Posted July 15, 2014 if you have used the generic KMS key in your build or answer file activation should be silent. on one of the laptops thats misbehaving if you manually set the ip/host and port of the KMS server does it make a difference? you should also get an error/success message in the console window what does it say are they stand alone or members of your domain
Joanne Posted July 18, 2014 Author Posted July 18, 2014 They are on the domain. When I run the script it activates fine. I don't know how to set the ip of the KMS server... is it part of the slmgr.vbs script?
Joanne Posted July 21, 2014 Author Posted July 21, 2014 (edited) slmgr.vbs /skms x.x.x.x slmgr.vbs /ato This worked for Windows. Now I have a Toshiba Tecra which will not activate office 2013. The one thing I changed was setting the KMS server to have a static IP... "The Software Licensing Service reported that the product could not be activated. No KMS could be contacted. Please see the Application Event Log for additional information." In the application logs I get an information event saying that it has sent an activation request to the KMS server... Note: I set up my machine to be a KKS server too, but re-imaged it since, could this have some effect? In the logs this client is looking for my old KMS server too. How do I get rid of this? I hope it isn't DNS digging... Edited July 21, 2014 by Joanne
SHimmer45 Posted July 21, 2014 Posted July 21, 2014 the KMS needs to have a static ip as there is an entry in DNS (srv _vlmcs record) if this IP isnt the same as your host clients wont be able to "find" the activation server. check the DNS record matches your host. btw if you install windows/office with a KMS key that machine will attempt to publish itself to DNS as a KMS server. make sure you havent got duplicates in your DNS
Joanne Posted July 21, 2014 Author Posted July 21, 2014 My DNS is bob on. I don't use the KMS key to activate, only the generic KMS key off microsoft technet... which activates the machine fine if I slam it in. Everything seems to be working, just not automatically! More info on the KMS server: it's a VM on the DC. Windows 7 Pro. When I looked at DNS event logs on the DC, there were a couple of errors regarding the DC itself. But this won't make any difference to the VM stored on it will it?
sted Posted July 21, 2014 Posted July 21, 2014 no but your kms server needs a fixed ip as it dosent look at the pcs name it looks at the vlmsc part of dns and iirc that dosent update so even if kms-01 is pingable it wont work as a kms server on a new ip unless youi change the dns entry for it if you use the generic kms to activate you are using kms you ONLY ever use your KMS key on your KMS server
Joanne Posted July 21, 2014 Author Posted July 21, 2014 Yeah it's in there. I have assigned it a static IP now. I've deleted the record of my old 2nd KMS. I don't have a machine to test on now... Have to admit that this is the first proper working KMS I have ever set up, so there are going to be stuff wrong I would imagine!
sted Posted July 21, 2014 Posted July 21, 2014 Yeah it's in there. I have assigned it a static IP now. I've deleted the record of my old 2nd KMS. I don't have a machine to test on now... Have to admit that this is the first proper working KMS I have ever set up, so there are going to be stuff wrong I would imagine! [ATTACH=CONFIG]25808[/ATTACH] there isnt much to do wrong. give a pc/sderver a static ip. feed it the kms key wait till you hit your activation requirement leave alone
Joanne Posted July 21, 2014 Author Posted July 21, 2014 I think it is probably going to be an issue with my image then perhaps... Toshiba's have some quirky problems when it comes to WDS!
sted Posted July 21, 2014 Posted July 21, 2014 I think it is probably going to be an issue with my image then perhaps... Toshiba's have some quirky problems when it comes to WDS! tell me about it 40 mins before i was due to leave ive had a tosh c50 dropped on me that needs doing. current;ly waiting for mdt to update the deployment share (had drivers on a pendrive luckily) cos they use some odd card grrr
sted Posted July 21, 2014 Posted July 21, 2014 those are what I have! Is it a C50-A-1MX? close but no cigar its an C50-A-1mm
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now