Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 801
  • Last Modified:

SBS R2 security lockdown or permissions - Cannot install devices

I have 2 servers in the company. 1 is a brand new SBS 2003 R2, the other is Server 2003 standard SP1.

I have 2 modems - Netcomm Mega I Modem (CD2002) and Netcomm Roadster II (AM5693). When installing them, I get an error pop up window "Windows was unable to install the modem". Then is finished the installation with an error, and detects the modem and tries again in a loop until I cancel the process.

I downloaded the latest drivers off the Netcomm website.

I cannot even install the modems manually on COM1 as Standard 56000 bps. I get the same message.

The event log shows EventID 256, Source: PlugPLayManager, Type: Warning.
Timed out sending notification of device interface change to window of "ModemDeviceChange"

There is no other error in the log.
 
I also found that I cannot install USB printer drivers on any new PC (Win XP) in the domain. The same symptoms appear. It goes through looking for the driver, displays the compatibility issue, then comes up with the error, and goes through the cycle again. Exiting USB devices work just fine.
 
The event logs don’t show anything unusual except Event ID 20, Source Print – which is a warning.
 
I suspect that a registry key may have been introduced or set since the introduction of R2, which is causing this problem in the domain.
 
The new server SBS R2 server was set up using the swing migration. Everything else appears perfectly fine. One thing, which may or may not be important – I took the old server (after the swing), and removed it from the domain (also removing the domain) using dcpromo – last DC scenario. Then, I renamed the server, rebooted, and set it to workgroup. After this, I rejoined it to the domain as a new member server.
 
As I said, all things appear to be working well. The only problem is that I cannot add any new hardware. All the old hardware still works fine with pre-existing drivers.
0
powerbiz
Asked:
powerbiz
  • 3
  • 2
1 Solution
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
SBS doesn't really like USB modems.  If the Mega-i is SERIAL then it should work.  However you should check to make sure that it's listed as supported hardware in the Windows Server Catalog http://www.windowsservercatalog.com

I'm confused about your comment regarding the old server... if you did a swing migration, is this because the old server was an SBS?  If so, you cannot rejoin it to the domain.

Jeff
TechSoEasy
0
 
powerbizAuthor Commented:
The problem is not limited to just modems. As I mentioned, new printers won't install either. I got some messages regarding Generic Volume Shadow Copy driver not installing. After a reboot, this message disappeared.

With the old server. I did a swing migration. Therefore, the old server was left out of the equation after the swing.
While it was disconnected, I removed AD (dcpromo) from the old server and brought it back to a normal Win2003 server in a workgroup.
Then, I renamed the server and gave it a new IP address. Then I joined it back to the domain as a member server (no AD).

Thanks,
Boon
0
 
powerbizAuthor Commented:
Sorry, I have been actively trying to solve this issue despite the lack of suggestions or interest. At this stage, I have manged to fix up the intial problem by runnning DCGPOFIX.

However, the installation now terminate with "cannot install this hardware ... the required section was not found in the INF" AND I cannot manually add new modem devices from Control Panel - Phone and Modem Settings, ADD device. Nothing happens when I click the Add button.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Sorry, I must have missed your last response.  There's certainly no lack of interest in helping out... but if your question doesn't get responded to in a timely fashion, please just post a quick "ping" reply so that it generates another email to me.

Back to the matter at hand...

I am still confused about this "old server".  Was it originally an SBS?  And then you now are calling it a Standard Server 2003?  Or was it always a Standard Server 2003?

Also, since it seems as though these issues arose out of your Swing Migration, did you contact www.sbsmigration.com at all to ask them for assistance?

Jeff
TechSoEasy
0
 
powerbizAuthor Commented:
It was a standard server 2003. I migrated the domain AD over from this server to the new one using the Swing migration. Everything worked fine.

This old server was not reintroduced back into the domain after the new SBS2003 server went online. While it was offline, I removed the AD manually from this server, and brought it back down to a workgroup server with no AD. I renamed the server as oldserver. Then I reintroduced this back into the domain and joined it into AD as oldserver. It was NOT promoted to be a DC. It is currently sitting as a member server in the domain.

I have spoken with several MVPs here in Australia, leading to the DCGPOFIX attempt. At least we have seen a bit more progress not.

After this latest attempt, one of my workstations has successfully applied the latest windows updates, which would not install before this.

Thanks.
0
 
AnnieModCommented:
PAQed with points refunded (500)

AnnieMod
Cleanup Admin
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now