Troubleshooting WDS: Event ID 257 – 258 – 266 – 513

Windows Deployment Services depends and works directly with Active Directory and DHCP, meaning that if any of those two servers are significantly modified, then probably you will not be able to start the WDS service and get the events ID: Event Viewer from WDS Server Event 257: An error occurred trying to start the Windows Deployment Services server. Event 258: An error occurred trying to start the Windows Deployment Services image server. Event 266: An error occurred while to refreshing settings. Event 513: An error occurred trying to initialize provider WDSImgSrv from C:\Windows\system32\WdsImgSrv.dll. Windows Deployment Services server will be shutdown. Disclaimer Please note that the following possible reasons, are related when all those events appear simultaneously and with the same descriptions. Event ID 513 can also appear regarding to a PXE provider error: “An error occurred while trying to initialize provider WDSPXE from C:\Windows\system32\wdspxe.dll. Windows Deployment Services server will be shutdown”. This particular error could happen for several reasons, like installing on the same server a System Center Configuration Manager PXE provider that replaces the WDS. Possible Reasons Those particular errors appeared when there were changes on Active Directory that did not were performed smoothly: – Changing a Global Catalog from Domain Controller. – Shutting down an active Domain Controller. Solution To solve this, you need to insert manually the FQDN of the domain controller working as a Global Catalog. 1 – Open the WDS snap-in and access server properties. […]

Read More →

Hyper-V Server: Installing, configuring and troubleshooting

It’s been a few weeks since its release but I finally managed to put my hands on to Hyper-V Server. I was very curious about it: A free operating system released by Microsoft working only as an HyperVisor it makes wonder about a lot of things. Also recently I’ve been working with VMWare ESX Server 3i, that is also the hypervisor working directly on the machine, and I had a good experience (I really loved the monitoring and reporting features that you can use). From the moment I started using Hyper-V Server few troubleshooting tasks needed to be done. Installing Hyper-V Server If you ever installed any operating system, ever, you should not have any problem with this. You’ll of course see that the process is identical from Vista and Windows 2008. To get started with Hyper-V Server there’s available the Hyper-V Server 2008 Configuration Guide. If you want to avoid almost any command line to be executed from now on, Hyper-V Server has a simple tool where you’ll load a menu to access most of the configurations you will need. You can access it using this cmd: C:windowssystem32hvconfig.cmd But I’ll execute the next steps using the command line features, so this procedure will apply as well for Windows 2008 Server Core. Managing Remotely To start using Hyper-V Server you will need Hyper-V Console on your Vista SP1 (remember: there’s no other option for an Hyper-V Server to be managed […]

Read More →

Common issue using Team Foundation Server with an external connection: Documents and Reports items becomes unavailable

Team Foundation Server is a very useful tool for team work, badly designed (no secret about that), but useful. The definition itself for TFS almost obligates you that this tool must be accessible not only from the internal network from your company, but also must be from external networks and the Internet. That’s when the problem appears. If you use Internet as the media to connect to TFS, probably you have this issue: even with all the permission in place, the Documents and Reports items from Team Explorer becomes unavailable. Like you know, you can use the FQDN (fully qualified domain name) of the Team Foundation Server name as the connection’s name with Team Explorer, for example: server01.domain.com. Or even you can use the server’s IP. But what happens if you want to work at home with any project within TFS?. If you don’t have a VPN (virtual private network) at your organization to make valid connections with Active Directory it can be very difficult to accomplish that. First you must achieve that you actually have a FQDN available to be used over the Internet. For example, if you own a web site for your organization, like http://www.mycompany.com, you can add a DNS record (tfs.mycompany.com) as a valid connection for your server. This post it’s intended to solve the named issue for TFS and not to guide you for a proper configuration of TFS over Internet, we can dedicate that […]

Read More →

Troubleshooting DCDIAG error: RPC Server is unavailable

It’s a common best practice to run the DCDIAG tool in all DC in your forest whenever a significant change has been made, i.e. a new DC has been added or deleted in the forest. With this you are testing if the change you just made was done correctly. It’s also common that if you have at least two domains in your forest (and the trust relationships in place), when you run dcdiag in any DC you get a message indicating that when the test of replication on a specific server applies, it fails indicating that the “RPC Server is unavailable”. Well, if you see this message you probably check if that the RPC service is up and running on the server… running in cmd “net start rpcss”. But the command prompt answers you, “don’t worry dude, the service was already running”. “Alright then…” you say, “Let’s try DCDIAG again”… and you get the same error like the first time… And then you go like “Hmmmm… why do I keep getting the same “RPC Server is unavailable” error?” And then I say “I know why dude!”… And then you “You do? Is there any way I can solve it?”…“Of course, why I’ll be posting something that I don’t know the answer!”… and then… OK, enough with the theatre… This issue appears when the configurations between the different DNS servers are not compatible. It’s something like this: you have a correct […]

Read More →

Troubleshooting a special case for domain controllers and DNS servers

“My DC is online, the TCP/IP it´s OK, the DNS service running but I still cannot make a valid connection with AD! “ This is a problem that can be present in many ways. The most common example is: you have your DC completely configure for Active Directory, the DNS server too, and you try to join a workstation to your domain and the following error appears: An Active Directory Domain Controller for the domain [yourdomain.com] could not be contacted.Ensure that the domain name is typed correctly(…) First of all, the obvious: Check that the connectivity is working fine… the DNS server and the DC both of them responds to PING requests. It’s most likely that if you cannot connect to the domain, the PING requests for the FQDN (such as: ping dcname.yourdomain.com or ping yourdomain.com) will not respond as well… but with the IP parameter should be working… if it’s not, then there’s definitely a connectivity problem, a bad TCP/IP configuration or a firewall within the way . Well, let’s see, this is a problem that can really make you nuts trying to solve it. Let’s assume that you have the correct configuration in your DC and workstations. If you have a DHCP server in you network, check that he is doing his job… giving the correct IP address for the workstations, the subnet mask, the DNS server and the other parameters that you are using. DCDIAG really? Can […]

Read More →