I got this message installing a HP CM1312 on an SBS server, how on earth it is justifiable that an SBS server doesnt meet requirements is beyond me, obviously this being a network shared printer this was no solution so I had to install it. Even going to the HP website you get the same installer package so you can't use the add printer wizard... a few hours with HP later and finally we cracked it. So to get past this error simply hold down CTRL + SHIFT when pressing Cancel on the installer, this will then keep the installer running passed the error and works a treat. Enjoy! Did I solve your problem? Buy me a virtual beer by clicking on a Google ad :). Thanks!
Popular posts from this blog
The Future Of Food Get £10 off of your first order of Huel with a minimum spend of £45, the equivalent of 28 meals. Huel gives you everything your body needs, its made in the UK and if you order today, it'll be delivered free tomorrow. Huel is a nutritionally complete powdered food that contains all the proteins, carbs, and fats you need plus at least 100% of the European Union's "Daily Recommended Amounts" of all 26 essential vitamins and minerals. So you know you won’t be deficient in any essential nutrients. Claim £10 off here: URL: https://huel.mention-me.com/m/ol/jj9uo-0d445f52d9
I have to admit, out of all server installs I have ever done, I have probably had one of the worst experiences ever recently with 2008 SBS. I thought I would blog about this problem simply because I was in a mess and I'm sure anyone else in this scenario would want to get out of it just as quickly as I did! My Scenario At first the clients were complaining that the Exchange was down, I noticed that the store service wasnt running so quite rightly I tried to start it but it wasnt having any of it. I went to Event Viewer and it had items like "Cannot connect to Active Directory" and "Exchange topology not starting" amongst many others. My most stupid mistake at this point was to reboot the server which is where I ended up watching a spinning wheel at "Applying Computer Settings". I couldnt think what it was until I found that it could be affected by IPv6 at which point it became clear that this definately was the problem, I had turned it off the d