• Announcements

    • Terry (WGS)

      WGS Forums Will Close on January 31st 2017   01/18/17

      Hi everyone, We're coming up to We Got Served's ten year anniversary and I've been taking a good look at the site to work through some plans for the future. I wanted to give you all a couple of weeks notice that I'll be closing WGS Forums at the end of this month.  As you'll be aware, the forums were opened to support Windows Home Server users and have done so brilliantly, thanks to everyone's participation. However, with each day that passes, there are fewer and fewer WHS deployments out there, meaning that forum registrations and traffic has now dwindled. I've tried a few times over the years to test some forums on related or adjacent topics, however, they simply haven't caught on. It's clear that these were always going to be predominately Windows Home Server forums and, with the passing of that platform, they've served their purpose well. So, please take some time to archive anything you need over the next two weeks. Access to the forums will end on Jan 31st 2017. Many, many thanks once again for your participation and support here. It's been a great community! Very best wishes Terry

Guido Beijderwellen

  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Guido Beijderwellen

  • Rank
  • Birthday 12/05/60

Contact Methods

  • ICQ

Profile Information

  • Gender
  • Location
  1. I used to work with Teamviewer to connect to my home servers over the Internet. This worked flawlessly with previous versions of Teamviewer, but starting with version 7 I no longer can connect to WHS. All other systems (Windows 7, Windows 2003 STD etc) work, only WHS refuses. A connection is made when connecting Teamviewer to the "partner" and the connection window minimizes, but the Teamviewer connection screen does not pop up. The strange thing is that when I connect to WHS using a plain RDP session and then also start Teamviewer, it does work and the Teamviewer connect window does pop up. Does anybody else uses Tramviewer 7 to connect to their WHS? And does it work?
  2. OK, my bug report at the MS Connect Homeserver area id# 401559 has been "upgraded" from the backup team to the design team. I have reported the issue even though I noticed that MANY people have the same problem but under many different circumstances. I understand that there are many reasons/problems that can lead to this 81% phenomen and I greatly appreciate the support of the Homeserver team. But on the other hand I agree with what others say, that it IS a big flaw when the main functionality of the product is causing so much problems. Microsoft now also places the Homeserver into the Small Business segment. But as long as it is performing that instable with restoring individual files I think it's not acceptable. The process of restoring individual files must be improved dramatically, if not I will stop with further implementing Homeserver both in the private area as in Small Business area. I am testing with the following systems: Laptop with Vista Ultimate - all views (also backups of other systems) at 81% stops with the wellknown error. Laptop with XP - hangs at 81% (also with other backups) Desktop with Vista Home - CAN view and open ALL backups. Even from other systems!! Desktop with XP Home - can open some backus of other systems, but NOT it's own. stops at 81% Laptop with Windows 7 - Any backup view pops up the error: "You need to format the disk in drive Z: before you can use it" Because on at least one system I'm able to open backups, even those of other systems I guess that it is an obvious clientside issue and not on the Homeserver itself or backup database. Maybe other software on the clients that is conflicting? This is the moment where it all fails: ERROR: waiting for the read/write drive to appear failed at restoreoffproc.exe -v 0 -x 121820832 (Mountbackup.log file) I hope Microsoft is able to get this one really solved...... Guido
  3. Correct: Without the quotes! In order to rdp to the full desktop I now use: mstsc /admin /v:[homerserver-name] Guido
  4. I logged on to the console of the WHS, so with a lcd screen & keyboard attached to the server. Then start menu, Programs, Administrator Tools, Terminal Serverices Configuration. On the Connections link there should be a connector in the right screen. In my case this was empty after I deinstalled some WHS Add-ins and after installing a new driver for my Intel Network card. I had to recreate the RDP Connector. After that I was able to RDP again or connect to the WHS Console. You can add a new Connection by selecting the Connections entry, click right on it and choose "Create New Connection". After the connector is restored, check the settings. Double click the connector and open the tab "Environment". Choose "Start the following program when the user logs on": and set it to: C:\Program Files\Windows Home Server\HomeServerConsole.exe -b Done. Hope this helps in your case as well...
  5. Perfect Drashna !! That's the solution! Many thanks for your quick response! Guido
  6. Hello Homers! After a problem with the NIC and deinstalling the Outlook Add-in the RDP connector got lost. So I could no longer logon via RDP but also (from the clients) the WHS Console no longer worked.. So I sat down behind my WHS, connected screen and keyboard..... re-created the RDP connection in the Terminal Services Configuration and added the console (HomeServerConsole.exe) as startup program instead of a full desktop. This works again now, however it looks a bit different then the original way the console was opened.. Now the console opens in a "sub" window... What is the original setup of the RDP connector of WHS? (see attachment jpg) Or how can I restore the original config? Guido
  7. I have the same problem as many other users aparently have. Tried all the proposed methods to solve it: permission script (cacls), removing the driver during restore, clean-up the database, reinstall connectors, restore home server etc. nothing solved the problems. I have the following clients: - Vista Ultimate Desktop Acer - Vista Home Premium Desktop - Vista Ultimate Laptop Dell - XP Sp3 Dell Windows Home Server PP1 licensed. Including all Windows updates etc. None of the clients is able to restore a single file using the connector. 1 system (Acer) is able to restore single files form the Laptop, but not it's own files !!! On top of that it's not possible to restore single files from client backups on the home server itself. Why is this all not working and when I read so many problems, why is it still not solved? Isn't it strange that we are not able to recover files on the "backup" server itself? Is the problem that difficult/complex to solve? When so may people have the same problem hasn't this come up during (beta-) testing?