Jump to content

Recommended Posts

Posted

Afternoon all.

 

Well, this is the most technically embarassing post I think I've ever had to write.

 

We have some new Surface Pro 7s for staff along with Classroom Pens 2. The pens do not pair with the devices and I can't find anything to show the process.

 

All devices are new and batteries are installed (the correct way). Nothing seems to let them pair with bluetooth, although one spec page for the pens seems to indicate they don't use bluetooth. Other notes say to hold the top button in for 5-7 seconds, but there's no top button.

 

We've tried all other buttons on the device but still not joy.

 

Has anyone got these things to work before we pull all of our hair out!

 

Cheers.

Posted

Thanks tapb for you help.

 

This is what is strange. I've never had to do anything before to get a Surface pen working. The unit is a Classroom Pen 2 and should be supported by the Pro 7. I initially assumed bluetooth as the pen does take a AAAA battery and has some buttons on it.

 

Currently nothing happens when the pen is touched on the screen. No support apps allow drawing and even pressting the pen on the Start button causes nothing to happen. Never seen this occur before with earlier Surfaces or similar tablets.

 

We tried a few pens and the same thing is happening (i.e. nothing). I'm going to try a reinstall of the driver pack for the Surface and see if that does anything different.

Posted

Writing on the screen does not require any pairing.

First check the AAAA batteries are in then and around the correct way and test it on another Surface device (if you have any).

If you've got any other Surface pens try them on the new devices to check the drivers.

  • Thanks 1
Posted

Well, note to self: Never assume a driver pack is installed.

 

Looking back over our process, we installed the Surface with our base image from MDT. Looks like the full drivers did not get picked up during updating. Everything was listed in Device Manager and so I assumed no issues - wrong!

 

Driver pack MSI from Microsoft appears to have fixed it. I noticed a slight change in screen colour too, so there may be a few other minor changes in the new drivers.

 

Thanks again tapb for the suggestions and hopefully this might help others who fall for the same mistake.

 

Cheers all.

  • Thanks 1

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...