Marsden

You need to learn http://www.technet.com 30 seconds of searching and I found this: http://www.microsoft.com/technet/prodtechn...81dd09b015.mspx Browse the link and learn how to deploy IIS 6.0

Have you configured your server for the role as a streaming media server?

If you use GPO correctly, your users can only run programs you specify. You can lock that down to a specific version number of the program. You can disable everything else a user might try other than the programs you allow. If you want programs A,B,C to run and nothing else; you can lock it down. No Control Panel, DOS prompt, no IE, nothing but the programs you specify. They won't be able to install anything either. Do your homework...

XP Pro x64 code is based on Windows 2003 Server with SP1. Don't confuse SP2 for x86 XP Pro (32bit). They are not the same!

SP2 does not require SP1 in order to install. Is her machine free of viruses and spyware?

You can't. You need hardware with 64bit driver support. Either your current modem manufacturer will supply 64bit drivers or you will have to locate and purchase new hardware that supports 64bit drivers. There are no work arounds for this.

Hate to disappoint you but there will be no "retail" SKU for XP Pro x64. Your only choices will be an OEM install or a trade up through MS.

What an interesting effect a reporting tool has on users. Bootvis only reports... it's not a tweak tool! Live the fantasy!

$11.95 and NO security... What a deal! username and password sent as clear text... Portability verses security... hmmm. I'll take security for free Alex...

With a plain old users account, remote users can't access stuff other than what's on the Remote Web Workplace screen. You want their shared folders and that is what is there along with their email. The SBS 2003 setup creates two primary sites for user access, the Windows SharePoint Services intranet (companyweb) and the Default Web site (including portal site, Remote Web Workplace, and Outlook Web Access). SBS 2003 is not an ideal location for hosting customer or user-facing business Web sites; an ISP can provide better performance and availability for these sites. However, it is recognized that the organization may need to create Web sites on the SBS 2003. In such a case, they need to be distinguished using host name headers. Host name headers are configured using the following procedure: 1. Open the Server Management console. Go to the Internet Information Services snap-in under Advanced Management. 2. Open the Web Sites container, right-click a Web site and select Properties. 3. On the Web Site tab, click Advanced. 4. Click Add. Enter the IP address of the server, TCP Port as 80, and the Host Header value. Default Web Site (Required) The Default Web site can be broken up into the following two identities: • Entire Default Web site: The Default Web site is used by internal users and contains links to the Remote Web Workplace. External users should not view the Default Web site in its entirety, unless they are connected through VPN. The Default Web site contains links that only work on the internal network. • Remote Web Workplace: Remote Web Workplace is specifically used for external access, but it is also used by internal users. In the “Web Server Certificate”, an SSL certificate is installed for portal.whateveryournameis.com. In this section, the DNS servers and Web sites are configured to make the Default Web site available for internal users using the name portal.whateveryournameis.com and on the Internet using a name, such as remote.whateveryournameis.com. Consider the following recommendations for configuring name resolution: 1. Add a host name header to the Default Web site, such as portal.whateveryournameis.com. 2. Verify that there is a name record on the DNS server in SBS 2003, linking portal.whateveryournameis.com to the IP address of the SBS 2003 Server. 3. Verify that there is a name record on the ISP DNS servers, linking portal.businessname.com to the static IP address on the external adapter of the firewall. 4. In the Server Management console, open the Advanced Management folder and expand the Internet Information Services node. Create a new Web site with a host name header, remote.whateveryournameis.com by right-clicking on Web Sites and selecting New->Web Site. 5. In the Web Site Creation Wizard, enter a Web site Description of remote.whateveryournameis.com and click Next. 6. Leave the IP Address (All Unassigned) and TCP port (80) at their default values and enter a Host header for the Web site. This should be remote.whateveryournameis.com. 7. Create a unique path under c:\intetpub for the remote.whateveryournameis.com Web site (click the Browse button and then select the New Folder button). Select the Allow anonymous access to this Web site check box, and click Next. 8. Accept all default properties and click Next until the wizard is finished. 9. Right-click the new Web site and select Properties. 10. On the Home Directory tab of the Web site properties, select A redirection to a URL and type the URL “https://portal.whateveryournameis.com/remote” in the Redirect to field. 11. Verify that there is a name record on the internal DNS servers pointing remote.whateveryournameis.com to the IP address of the SBS 2003 Server. 12. Verify that there is a name record on the ISP DNS servers pointing remote.whateveryournameis.com to the public external IP address of the small business firewall. By using a Web redirect, the single SSL certificate provided on the Default Web site is valid for use both when internal clients connect to http://portal.whateveryournameis.com and when external clients connect to the Remote Web Workplace through http://remote.whateveryournameis.com. Accessing CompanyWeb Externally (Optional) The SBS 2003 setup creates a Windows SharePoint Services intranet site available within the small business network. It is available internally using the following URL: http://companyweb or http://companyweb.whateveryournameis.local. By default, the intranet is configured for use only on the internal network. However, it can be accessed through VPN. SBS 2003 can't be configured in TS mode to run applications. You would have to install Windows TS 2000 or Windows TS 2003 on top od SBS 2003.

Where does keeping an open mind offer justification for throwing the EULA out the window. You are not happy with the current limitations of your copy of XP x64. There is a huge difference between slip-streaming your OS and hacking a file that limits your use of a PID. A competent attorney would tear your "open mind " defense to shreds in open court.

From the EULA.txt

Why is this sooooo important???

Remote Workplace is encrypted via SSL. You need more security than that? Install SharePoint and you've got your shared folders.

What retail product do you have? As far as I know it is NOT in the channel yet having just been released to manufacturing. Changing the key would be in direct voilation of the EULA.

You are fretting over 1.3 MB missing??? SP1 must have been really hungry

MS has all the info you need. Check it out on Technet.com.

Buy a faster PC!

I hope the program is not 16bit because if it is you are sh** out of luck. There is no support for 16bit or DOS apps on x64. No compatability, no work arounds, no hacks...

It's called Remote Workspace...

So what part or parts or Remote Desktop can't do what you just specified? RDP is encrypted and secure.

Yes. Why would they withdraw their offer?

How about Port Forwarding on the router? You have to forward port 3389 from the public IP address to your internal private Ip address. If you want to use all the SBS remote features you will want to forward ports 443-444, 1720-1723, 3389 to your server's private IP address. To use OWA (Outlook Web Access) you type in your public IP address like https://xxx.xx.xxx.xxx/exchange or https://xxx.xx.xxx.xxx/remote

I'm always amazed when folks think MS is weak on product and security. They have created tools by which companies are getting their work done. If they weren't successful, MS would be but a bad dream. Please explain why a recent report from Yankee Group with their North American Linux Windows TCO Survey shows 88% of of corporations report that Microsoft Corp.'s Windows Server 2003 operating system provides equal to or better performance and reliability than Linux in comparable usage scenarios. Those are the results of Yankee Group's independent, non-sponsored North American Linux Windows 2005 TCO Comparison survey. The results indicate that Microsoft's continued attention to hardening the core Windows operating system yielded tangible performance improvements. The 88% of corporate customers who rated Windows performance equal to or better than Linux is a 12% increase from the 76% of customers who ranked Windows on a par with Linux in Yankee Group's 2004 TCO study. The survey responses also show that Linux is no longer a pristine Utopian environment. The increasing popularity and deployment of Linux and open source are making it prey to the same TCO issues that have long plagued their Microsoft Windows counterparts. Additionally, the Linux market is beginning to experience "forking" or fragmentation among the various distributions and customized code. There is a high probability that this will increase interoperability and integration issues. Corporate customers are already concerned about this. In summary, Linux and Windows each have specific strengths, weaknesses, opportunities and threats which can impact a corporation's TCO and ROI, positively or negatively. To achieve optimum results and avoid undue deployment problems and expenses, corporations must perform a thorough cost, performance risk analysis to determine the right technology option. Any business that does not know or cannot determine the key costs associated with its software infrastructure risks making the wrong technology decision. Such a mistake may adversely impact the TCO of their respective environments for years. By Laura DiDio Senior Analyst Yankee Group Boston, Ma.

When you share the resource did you selet Everyone on the Permissions tab? Create a User account on each machine with the same name and password. Do no use the Administrator account. You do not need a server in a peer to peer arrangement. Each PC on your network can support 10 concurrent connections from other machines. Make sure your XP firewall is not blocking printer and file sharing.