Talk:Windows Home Server

Untitled

There seems to be a fair amount of interest in this OS due to it being recently revealed to the public. I was kind of disappointed that the page had not had more in depth information as now is when a lot a people are apt to go looking for basic info. My technical knowledge is rather limited, especially in regards to server software, so I don't feel confident adding much to the page, but I wanted to encourage others. I've noticed a fair about of apparent misconceptions in the product and a muddy understanding of what it can and cannot do. In particular in regards to whether it can be used by systmes other than Windows, like OSX or Linux. I saw one comment that suggest this will be possible. Also, I saw a video on MSDN's Channel 9 that was very informative that someone updating the page might want to check out. There was one part, if I understood it correctly, that said if someone knew what they were doing (ie. not a novice) they could use remote desktop to access much richer functionality than the basic control panel interface provides. It seems like much (if not most) of Windows Server 2003 can be accessed. Someone who knows this OS might be able to talk about what this could mean as far as an enthusiast using Windows Home Server as opposed to the novice user. I hope someone can use this information to flesh out the article. --72.24.86.95 09:47, 9 January 2007 (UTC)

I'm the GM for Windows Home Server and will try to update this article when I can. I already fixed a few inaccuracies as well as replaced the bogus/FAKE screenshot tha was original there with a real one.ckindel 23:21, 12 January 2007 (UTC)

FOSS alternatives/"See Also" section

I think their should be a section mentioning open source alternatives to WHS. WHS looks good, but people need to be informed that their are FOSS alternatives. FreeNAS and Openfiler in particular spring to mind. Personally I like FreeNAS because it has upnp support which allows you to stream media to an xbox360 without relying on Windows Home Connect.

--Jmantra 13:52, 22 July 2007 (UTC)

No for see also section. Links may be inlined, though. But I don't think the apps you specify are competitors to WHS. WHS is not a NAS server or UPnP media server (btw, Windows Media Connect has been deprecated in favor of Home Media Ecosystem (HME). Vista, Zune Media Player software, Zune music player and WMP11 includes HME servers; WMP11 for Vista and X360 includes clients). While they are a part of its feature list, WHS can act as host (application server) for applications written using the WHS API as well. --soum ^talk 14:00, 22 July 2007 (UTC)

While WHS isn't really a NAS server and those distros aren't really in direct competition with WHS, they both serve similar functionalities to WHS, so i think they are worth a mention.

I didnt say they should not mentioned, I said they should not be mentioned as being competitor to WHS. It can be mentioned as in "WHS includes shared storage akin to NAS servers like <insert the most common NAS server> here". Better still just stop at NAS (so that we dont take sides singling out a single product). NAS solutions are definitely linked from that page, arent they? --soum ^talk 15:38, 22 July 2007 (UTC)

i agree with Soumyasch. In addition, the other Microsoft OS pages don't have a list of competitors so it probably wouldn't be a good idea to break with that tradition. 128.54.42.248 18:41, 23 July 2006 (UTC)

Obsession with the number 10 it involves everything

Interface

Is it true that it can be connected from both the web browser and its own console program (Windows Home Console)?? Please clarify this --Jutiphan 23:51, 14 January 2007 (UTC)

Yes.

The Windows Home Server Console is a rich Win32 application that *executes* on the server. The UI is remoted to the client via the Remote Desktop Protocol (RDP). A small app running on a client PC provides a local window frame for this app making it appear that the app is running on the client (when it is really running on the server).

In the Remote Access scenario, the home administrator can access the Windows Home Server Console via a web browser over the Internet because the Remote Access webapp uses the Terminal Services/RDP ActiveX Control to enable access.

ckindel 01:26, 17 January 2007 (UTC)

Can WHS be used to run your own apps?

Is it going to be possible to install your own software (e.g. webservices) on this server, or will it be locked down like the 360? The 360 security rocks. It's the ONLY console that's never been hacked, and EVERYONE has tried. I might sleep better knowing it has hardware security like the 360. ...But I'll probably complain if they lock it. ....Then again, I think I'll complain either way. Yeah, I'm an impossible customer. So what's the verdict? Brien86 07:06, 22 January 2007 (UTC)

Yes.cek 17:04, 21 January 2007 (UTC)

Thanks, can I add that to the article? Brien86 07:06, 22 January 2007 (UTC)

Sure. I am a definitive source ;-). cek 22:11, 22 January 2007 (UTC)

Cool, so it can run, for instance, SQL server?PonThePony 10:11, 10 February 2007 (UTC)

It could (at least the beta can, during the install it says it's Win2003 SBS, not Web Edition), but that's not actually the point of the darned thing. --Blowdart 06:41, 27 February 2007 (UTC)

no worries, I've hacked many 360's and I've hacked the beta version of WHS. security sucks

So can newsreaders and P2P be run on it, which would make sense on an "always on" machine? —The preceding unsigned comment was added by 195.37.205.21 (talk) 12:34, August 20, 2007 (UTC)

Windows Home Server is NOT based on R2

Windows Server 2003 R2 is a release of Windows Server 2003 SP1 that includes a second CD containing new, optionally installed technologies (see Windows Server 2003 for a full list).

Windows Home Server uses none of these optional technologies.

Windows Home Server is based on the Windows Server 2003 *SP2* codebase.

Reference: http://blogs.msdn.com/danielfe/archive/2007/01/26/windows-home-server-for-hobbyist-developers.aspx

cek 03:11, 12 February 2007 (UTC)

windows home server seems to use the Small Business Server sku as it's base since the step after the winPE setup is the ms-dos text installer from that sku.

--216.193.153.184 (talk) 14:13, 30 September 2009 (UTC)

Judging by the presence of the SBCORE service, it's actually based on the SBS code base (which is SP2, not R2).218.214.18.240 (talk) 11:20, 10 September 2011 (UTC)

Judge by whatever you like, Wikipedia does not care: Original research is not allowed in Wikipedia. Either find a source for your assertions or give them up. And the blog post never says that they are based on the same codebase. It just says WHS is using the same technologies. So, what? Ubuntu is also using some of the technologies in Windows Server 2003 (e.g. SMB-based file sharing). Merely using the same technologies does not mean a similar code base. Fleet Command (talk) 10:36, 12 September 2011 (UTC)

Home Server team blog contains more information

The Windows Home Server team blog contains more details on the product that someone may want to incorporate here.http://blogs.technet.com/homeserver/

cek 03:32, 12 February 2007 (UTC)

Windows Server Comparison

I think that it would be good to have a comparison between the standard Windows Server (2003 or "Longhorn") and Windows Home Server so we know what Windows Home Server can and can't do. 220.237.189.10 02:09, 1 March 2007 (UTC)

I'm not so sure; yes it's running under 2003, and both share files and printers; but that's about it. Also there's already talk in the beta feedback forums of what services will be removed, so right now it's all up in the air. --Blowdart 11:35, 2 March 2007 (UTC)

Screenshots

I have a bunch of screenshots on my blog, which if anyone things will be useful I can upload here (if someone will guide me through how to do it and mark them as GPLed) --Blowdart 07:29, 8 March 2007 (UTC)

Official website on microsoft.com

[1] is now live.

I'd update the page myself, but the NPV rules prevent me from making such a change myself. cek 02:41, 28 March 2007 (UTC)

While i'm at it, why is the new External Link to the "Windows Home Server Forums" the first external link? That link is to an UNOFFICIAL forum (the official Microsoft forums are at http://forums.microsoft.com/WindowsHomeServer

Another piece of feedback, in case anyone wants do do some editing:

Under "Picing and Availability" it reads 'In a Channel 9 video interview, Windows Home Server General Manager Charlie Kindel said that early Home Servers will cost about the same as a low-end PC, or around $500.'

The Channel 9 link goes to the wikipedia page on Channel 9. That's cool. But shouldn't there also be a link to the video of me too, say like this:

In a Channel 9 video interview, Windows Home Server General Manager Charlie Kindel said that early Home Servers will cost about the same as a low-end PC, or around $500. cek 02:41, 28 March 2007 (UTC)

User Interface

It looks like Windows Home Server also has a own graphical user interface in addition to the one that can be accessed on a web browser, just like Windows Server 2003 has. Images of this can be found on Paul Thurrott's WinSuperSite. Off! 16:11, 21 April 2007 (UTC)

(Off topic) Am I alone in thinking the web interface for shared folders looks awfully lot like Windows Live Folders? --soum ^talk 16:39, 7 July 2007 (UTC)

10 PC's

Someone noted they cant find a citation for the 10 PC limit. I did a Google and Live search and, yep, sure enough, we have never said publically anywhere that there's a 10 PC limit. cek 03:15, 5 May 2007 (UTC)

There is one: http://blogs.technet.com/homeserver/archive/2007/05/04/speaking-of-the-number-10.aspx

More information

This article needs information such as: the build number and beta number or release candidate number of the latest preview release version of Windows Home Server. 76.183.213.20 22:53, 9 June 2007 (UTC)

(I was formally known as IP address: “76.183.213.20”) Hello, anyone there?  Tcrow777  talk  20:18, 20 July 2007 (UTC)

Domain or Workgroup?

Does WHS set up it's own domain? Is it compatable with existing domains? 203.33.3.12 01:12, 19 July 2007 (UTC)

It doesn't include a domain controller. --soum ^talk 04:44, 19 July 2007 (UTC)

Nor will it fit into a domain network. It's for home, there's no domain support. --Blowdart 22:51, 2 September 2007 (UTC)

It is possibale to setup home server rtm as a domain controlor all u have to do is remote desktop to the server goto system32 then type dcpromo then goto the dcpromo.exe to start the domain controllor setup 58.174.66.52 (talk) 08:35, 9 May 2008 (UTC)

See http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=1434320&SiteID=50 for some discussion of this topic. — JBazuzi (talk • contribs) 16:39, 9 May 2008 (UTC)

I just reverted a change that claimed that WHS could be a DC and could join a domain. Both of these claims are contradicted in the article under Compatability, and the claims didn't cite a source, and the contradict the sources we know about.— JBazuzi (talk • contribs) 00:34, 13 June 2008 (UTC)

Comparison with similar products section

The section is full of OR. How is this anymore like Server 2003 web edition without looking like the rest of Server 2003 family? And because both are family members of the server 2003 family, how can we say that home server is built off the web edition codebase (as the secn seems to imply) and not off the codebase of which both web edn and whs are built? Its not verifiable, I'm removing it. --soum ^talk 19:36, 20 October 2007 (UTC)

I've been on the microsoft certified professional course, so maybe I know something you don't? Besides I also linked to the OFFICIAL MICROSOFT BOOK on the subject! Available on Amazon, if you want to buy it. If you think it biased, then by all means edit. But also please learn the difference between 'unsourced' and 'I don't own that book'.ANTIcarrot 23:23, 22 October 2007 (UTC)

Two things: One, Soumyasch is a Wikipedia administrator and seasoned editor; you should trust the knows what he's talking about. Second, please read up on Wikipedia's original research policy. If you want to make a claim that the features of WHS are also available in XP, fine -- find a reliable, peer-reviewed source that makes this same statement and explains itself adequately. It' also not really useful to write stuff like, "yeah, well, if you add all these other third-party pieces, you'll get something similar". That goes beyond the purpose of the article... all we need to do in this article is describe the product itself. -/- Warren 00:28, 23 October 2007 (UTC)

@ANTIcarrot, no one is going to buy and read a damn book (or even a free web page for that matter) to know something; they are going to read an article for that. Looking up is for verification. If what you say does not satisfy the user's need of information, it does not belong in the article. The questions I raised were not answered in the article.

Plus, does the book you cited compare WS2K3 and WHS? If not, the comparison must have come from you. It is your original research then. It is not verifiable independently by others. As such, it is not includable here. I am sorry to say, but you (or me, or any other Wikipedia editor, for that matter) do not constitute a reliable source and your words are not acceptable in an article, no matter how many courses you have taken. --soum ^talk 02:34, 23 October 2007 (UTC)

I vaguely recall a policy stating that blatantly obvious things do not need sources. "The sky is blue." "10<100" "Zeroth law of thermodynamics et all" Etc. And I don't recall any rule that requires sources to be free or low cost. Especially for highly technical topics. But if you want to 'interpret' the rules to mean anything you want them to mean, then fine. I have better things to do.ANTIcarrot 18:22, 25 October 2007 (UTC)

No one asked for a free source. All was asked was a reliable verifiable source to back up your claims. The secn stated, "As currently described it looks very similar to Server 2003 Web Edition", with absolutely no substantiation of the claim how so. It begs the question how it is similar to ws2k3we without being similar to other ws2k3 editions (thats not blatantly obvious). The secn does not answer that. No one is going to hunt a source down to know something (they might do it to verify the knowledge). Unless that is made clear, it should not be here. Next is "and the term 'add on' implies both are not capable of running regular x86 software". Where does "add-on" come from? And what is "regular and irregular" x86 software. The processor does not distinguish the ISA based on OS. None of that is blantantly obvious to make the connections on your own and still have it verifiable. Plus whats the point of the section? Why would one be interested in obtaining WS 2K3 WE when reading about WHS? And why would one be intersted in knowing what softwares and hardware one must hunt down to have equivalent functionality. I reiterate, the section does not belong here. --soum ^talk 18:47, 25 October 2007 (UTC)

Issues vs. Problems

"Issues" is an over-used and increasingly abused word. I recommend changing "issues" to "problems". Unfree (talk) 06:25, 21 February 2008 (UTC)

Under Known Issues -- No native backup, someone introduced a bullet that says that WHS is vulnerable to Fire, Theft, etc. Aren't all things vulnerable to this? And what does this have to do with Native Backup? Edward (talk) 05:38, 9 April 2008 (UTC)

That was me. I'll explain what I meant, and maybe a more skilled Wikipedia editor can figure out a way to make the page make sense. If you could automatically do a backup of all your WHS content to a web-based backup service, or to a friend's WHS in another part of the world, or to an external USB drive that you stored in a safety deposit box, you would be protected from fire & theft. Clearer? — JBazuzi (talk • contribs) 16:27, 10 April 2008 (UTC)

Knowledge base article solving issues

Blowdart - please leave my edit alone.

This article "Data files that contain NTFS alternate data streams can be corrupted on a Windows Home Server-based computer" http://support.microsoft.com/kb/943393 relates directly to the file corruption issues. Would you **please** read the article. http://support.microsoft.com/kb/943393 "Data files that contain NTFS alternate data streams can be corrupted on a Windows Home Server-based computer" This in turn leads to the download about signing streams. http://support.microsoft.com/kb/941914/ "An update for Windows Home Server lets you obtain a trusted certificate for your Windows Home Server computer during remote access configuration of your personalized domain"

I've got home server. This worked. Do you? Even if you follow the cited link for the issue eariler on in the article (ref 17), a sentence before the anti-ms vibe "even though" (http://support.microsoft.com/default.aspx/kb/943393/en-us) it actually takes you to 941914, the one you keep reverting!

ED: Okay, I'm sorry, looking up I see you have home server. Am I really wrong then? Is my home server just fluking *not* corrupting stuff right now?

Paulecoyote (talk)

The knowledge base article on the SSL certificate is for remote access; originally the devices had self signed SSL certificates. Just after launch MS changed that so it had an (IE) trusted root, and secondary certificates, doing away with any SSL warnings. The corruption KB article is wrong, it is not a resolution; I will see what I can do about getting it changed. --Blowdart | ^talk 15:12, 24 March 2008 (UTC)

I'm sorry, I was looking at 943393 which does have a fix, not 946676 which *doesn't* have a fix and is quoted in the article and mentioned before 943393.

Perhaps that paragraph ought to be reworked if they are two seperate but similar issues. I was certainly confused and am a little embaressed about how confused I actually was / am.

Paulecoyote (talk) —Preceding comment was added at 09:10, 29 March 2008 (UTC)

You're not the only one that's confused; I've reported it to MS and we'll see if the KB article gets updated. --Blowdart | ^talk 10:12, 29 March 2008 (UTC)

No revert war about Power Pack 1, please

In the "Native Backup" section, Contributions/81.23.56.25 added this text:

Update -as of 22/05/08 Microsoft has informed beta testers that this feature will not be present, and may not be released with the Power Pack 1 RTM.

I reverted this edit because it's an uncited claim. I haven't seen any suggestions, even in blogs, that the Server Backup feature won't be in Power Pack 1. My revert was reverted, without explinatation; I have reverted that revert.

Also, Wikipedia is not a news site; using "Update" style writing is not encyclopedic. Instead of adding a sentence that contradicts the previous one, better to modify the existing text to be correct.

Additionally, I don't think the date format and use of "RTM" match WP:MOS, but I'm no expert there.

Furthermore, I believe that all Power Pack 1 Beta testers are bound by an NDA. If Microsoft *has* told beta testers something interesting about PP1, and that beta teter shares that information publically, that may be a violation of the NDA.

Finally, 81.23.56.25 also reverted a good edit that fixed a typo ("add address"); I have reverted that bad revert, as well.

I will not engage in a revert war on this topic. I will not revert again. I hope that another wikipedian will help resolve the situation. — JBazuzi (talk • contribs) 15:00, 29 May 2008 (UTC)

Alternative Solutions?

I'm glad that WHS isn't the only option for a home server, but is the WHS page really the right place to describe them? I mean, they don't exist solely to be alteratives to WHS, right?

What I've often seen here on wikipedia is that various alternative to something are all in the same category. I find that very helpful when I'm looking for alternatives to a given product. — JBazuzi (talk • contribs) 22:58, 4 June 2008 (UTC)

That section was added yesterday; I've removed it. The Home server article is the appropriate place to look for a list of like software and products. A category will need to be created someday, but it doesn't seem like there's really anything out there just yet that is in the same class as WHS... -/- Warren 23:59, 4 June 2008 (UTC)

Plus without a comparison table somewhere how can you tell if it's a true alternative? What features are a must have to make it a true alternative etc.? I agree removing it was best. --Blowdart | ^talk 07:55, 5 June 2008 (UTC)

Power Pack 1, RC1

I'm going to start updating sections of this article which have been address by PP1-RC1. (Symo85 (talk) 04:37, 18 June 2008 (UTC))

I haven't updated the "No Native Backup" section, as I was a little confused by what was already there... I thought the situation (before PP1-RC1) was redundant backups (keeping a copy of the data on two physcially different HDDs) for information backed up from a PC was available, but not for information only stored on the server (and now with PP1-RC1 that limitation has been fixed). But a complete backup of the server was not possible (and still isn't). (Symo85 (talk) 05:31, 18 June 2008 (UTC))

I'm not sure wikipedia should be "recommending" pre-release software as a solution to file corruption problems; whilst it's unlikely RC1 will change much before release; it's not supported; nor is it an official solution as it's not released code. I've reworded the section. --Blowdart | ^talk 06:54, 18 June 2008 (UTC)

"Stay at home server"

Has anyone else seen this weird marketing thing at http://www.stayathomeserver.com/[2]? I tried looking up info about it on Wikipedia, but nothing will show up. I want to write something about it in Wikipedia, how would this be correctly done? Forgive me for formating errors, I am new at this. --James73686 (talk) 05:28, 25 June 2008 (UTC)

Actually I have that book :) However it's a marketing web site; unless it wins some awards I doubt it's suitable for inclusion. --Blowdart | ^talk 13:19, 25 June 2008 (UTC)

Windows home server as RDP gateway

"The system also acts as an RDP gateway, allowing remote control over the internet of supported internal machines on the home network." The explanation on how this should work is missing?

Its like Back to My Mac, but without needing to subscribe to the pay service of mobileMe

Windows Home Server uses Port 4125 from the external network (Remote Web Workplace (RWW)) and it uses Port 3389 on the internal network for connecting to clients http://mswhs.com/2007/06/28/what-ports-do-i-forward-in-my-router-for-whs/ --smadge1 (talk) 13:26, 3 November 2008 (UTC)

Cable network system can get hacked by WHS user on domain?

I came to know about WHS through an unwanted icon in my network places folder and systray that said find Upnp devices. and it placed an unknown named location on the same folder. which disappeared after a while as i was searching for the clue. any idea? 119.73.112.6 (talk) 10:07, 13 July 2008 (UTC)

Things that needed to be added to this article

Because I can't edit this article myself (NPV) here are some suggestions for flushing this article out further:

• Technology section should include:
  • Media serving (Windows Media Connect)
  • More deets on Remote Access and the Dynamic DNS service with the free SSL cert
  • 3rd party platform/SDK
• There should be a "Products" section that lists the OEM products that are available (or are no longer available as it were). For example, HP Media Smart, Fujitsu SCALEO (defunct), Acer, Tranquil PC, Lenovo, etc...
• Pricing only covers the system builder pricing (software). It should also cover the cost of OEM systems.
  • While I'm at it, someone should update the MediaSmart page to reflect HP's latest price drop.
• Add the issue of any directory with a "temp" in it is not backed up. People has lost data when they name their MP3 or photos as c:\mp3\temp.
• Support for compression and encryption in case of theft
• How to make a backup of the main WHS drive in case it fails
• How to install a regular OEM version with HP's SanEncore update with "Features For Mac" and Time Machine integration.
• The success or failure of recovery when one hard drive fails

 —Preceding unsigned comment added by 99.243.207.3 (talk) 14:22, 29 November 2009 (UTC) 

cek 21:00, 26 November 2009 (UTC)

I think that a list of OEM releases of WHS is a great idea. I'll see about adding some to this list. Beyond the HP MediaSmart server and the Acer Aspire are there any other mainstream ones? --Omgcapitalism (talk) 05:34, 7 April 2010 (UTC)

Yes, in addition to HP's MediaSmart you can find WHS producs from Acer, Tranquil, and many others. :-)

I added a citation in the Pricing section which links to Microsoft's list of OEM WHS boxes. I was going to add a new section but I suspected that it would probably be shot down as WP:Advertising. I think adding the citation in the pricing section is probably a good compromise. Let me know what you think. Omgcapitalism (talk) 05:11, 17 April 2010 (UTC)

Remove References Needed

With the number of in-line citations above 30 from a diverse list of publications, can the message box at the top be removed at this time? Mikebar (talk) 13:48, 9 July 2009 (UTC)

Better Screen Shot?

Can someone please replace the lame screenshot of the administrators desktop with something better? Like a shot of the home server console?

cek 21:00, 26 November 2009 (UTC)

Someone replaced the WHS Console screenshot with a terrible desktop screenshot again. Could it please be reverted? It's silly. JensRex (talk) 19:28, 21 April 2010 (UTC)

x64-bit windows server 2008?

Looking for a listing of all HP printers that have the x64-bit using windows server 2008, reason is that we have about 25 printers and we are trying to find out which ones have this availabity, thank you Brenda Lyles with Spartanburg Forest Products, Greer, SC 29651 blyles@gsponline.net

List of specific extensions and hacks for WHS?

I've been using a Acer Aspire WHS box as a development tool for a lot of my work with .NET programming and I thought that it might be helpful to share a few specific hacks somewhere in this article or perhaps in a separate leaf article. Here are some of the ones I wanted to share as references for folks interested in the extensibility and capabilities of Windows Home Server:

• Using Windows Home Server as a Print Server
• Installing DotNetNuke on Windows Home Server
• Using WHS as an Email Server
• How to Install uTorrent on Windows Home Server

What do you think? Does this belong on this article (maybe in a new extensibility section?) In it's own article? Not at all?

--Omgcapitalism (talk) 05:32, 7 April 2010 (UTC)

My opinion: those topics are interesting, but not appropriate for Wikipedia. They're not hard to find with a search engine. Maybe a good middle-ground would be something along the lines of "WHS machines can also be used like any other windows server, for example as a print server, email server, or torrent client." I also added torrent to the Addin list, since there is an addin for it. — JBazuzi (talk • contribs) 06:09, 11 April 2010 (UTC)

That's what I figured. Thanks for your input! Omgcapitalism (talk) 04:45, 17 April 2010 (UTC)

WHS 2011

The article correctly notes that the new version is out this month. The rest of the article describes WHS V1. The article should probably be updated to include both or rename this one and a new article for the latest version. Mikebar (talk) 18:28, 24 April 2011 (UTC)

Merger proposal

I propose that the Windows Home Server 2011 article get merged into this Windows Home Server article, since they describe the same product, and there are so few new additions in the 2011 version, so why have two articles for the same thing? 164.4.17.33 (talk) 14:00, 15 September 2011 (UTC)

• Oppose. They do not describe the same product. The other article is about the predecessor of the subject of this article. Both have perfectly established their notability and are allowed to be independent articles. This article has potential for expansion. Fleet Command (talk) 14:41, 15 September 2011 (UTC)

External links modified

Hello fellow Wikipedians,

I have just added archive links to one external link on Windows Home Server. Please take a moment to review my edit. If necessary, add {{cbignore}} after the link to keep me from modifying it. Alternatively, you can add {{nobots|deny=InternetArchiveBot}} to keep me off the page altogether. I made the following changes:

• Added archive https://web.archive.org/20091127011705/http://windowsteamblog.com:80/blogs/windowshomeserver/archive/2009/11/24/power-pack-3-instructions-for-users-running-pre-release-versions.aspx to http://windowsteamblog.com/blogs/windowshomeserver/archive/2009/11/24/power-pack-3-instructions-for-users-running-pre-release-versions.aspx

When you have finished reviewing my changes, please set the checked parameter below to true to let others know.

Y An editor has reviewed this edit and fixed any errors that were found.

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—^{cyberbot II}_{Talk to my owner:Online} 07:18, 22 February 2016 (UTC)

External links modified

Hello fellow Wikipedians,

I have just modified 3 external links on Windows Home Server. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Corrected formatting/usage for http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=2234532&SiteID=50
• Added archive https://web.archive.org/web/20101116023811/http://www.microsoft.com:80/presspass/press/2007/nov07/11-04WHSLaunchPR.mspx to http://www.microsoft.com/presspass/press/2007/nov07/11-04WHSLaunchPR.mspx
• Added archive https://web.archive.org/web/20091122215303/http://windowsteamblog.com:80/blogs/windowshomeserver/archive/2009/11/19/windows-home-server-power-pack-3-available-november-24th-includes-enhancements-for-windows-7-based-computers.aspx to http://windowsteamblog.com/blogs/windowshomeserver/archive/2009/11/19/windows-home-server-power-pack-3-available-november-24th-includes-enhancements-for-windows-7-based-computers.aspx

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Y An editor has reviewed this edit and fixed any errors that were found.

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 09:12, 1 January 2017 (UTC)