fizban2

runas "domain\administrator" "%systemroot%\regedit" /s <filename>

i have to agree, but in some cases it is nice to get things into production, even after SP1 there is the chance that you will find issues that are specific to you setup/forest/configuration. getting software out there you get to find the bugs your self and resolve them sooner, i know it can be a pain, and even more painful sometimes, but will make things easier in the long run

enable remote desktop through the advanced system properties, (can be found by right clicking the My computer icon and going into properties) from then in the left hand side click to enter the advanced settings. from there go into the remote tab and enable remote desktop, if this machine is part of a domain, add the AD groups you need to have access to it

when you burn the Vista ISO, burn the at lowest speed your DVD-burner has, btom, any chance you could expand on the issues you are having

if you are using Server 2003 R2, you can use the printer management to transfer those across, but if they are just network printers setup on that machine it will be faster to recreate them on the second machine

if you both have Internet IPs yes, if you have internal NAT Ips (192.168.x.x) then no, you would need something to connect you two to each other. hamachi is a free VPN type tool that would do what you are looking for

Implementing a 2 Node Exchange 2003 Sever Cluster Exchange 2003 backup and resstore with NTBackup

Subnet would only matter if your router could not send information accross different subnets, which doesn't sound like the case

been running test boxes of it since the 5000 build along side vista, beta 3 would be the first one that i would run production, now it is just convincing my management that it is a viable option.

is this an PX machine? does it have a firewall enabled?

adding alerts to the machine would be an easy way to do it as well, alerts can be setup in the preformance concolse. you could set it to something like if disk x is > 80% capacitiy, email person y

the motherboard in question should support vista, for a defianite anwser, check the motherboards manufacturing website and see if Vista is listed by the vendor as compatible

question has been anwsered closing the post

N1k is right, network discovery is probably still running, and since you probably aren't running longhorn server on the back end (though you might idk) nothing is taking advantage of it yet. this only happens the first time correct? after that ever is fine?

**pinned**

The Codec pack will allow you to watch a MOV file, you won't be able to edit it with movie maker. AVI's MPG or MPEG files are support by movie maker,

unistall your most recent patchs till you can find the one that changed this for you, once you know which one it is you will want to alert microsoft to let them know of the mix up

where is vista installed? if you just hook up vista and the IDE drive will it show up fine?

Vista by default is set in a balanced power save mode, after 1 hour it will put the computer to sleep. once it is in sleep, you will lose net connectivity, this is probably why it isn't working. check the power settings and change them to somethine else, or turn it off. Try it then from work, can you RDC to another machine at home? is it possible that the RDC ports got shutdown at your work?

if you boot into safe mode do you get the same error when loading the network center? try booting into safe mode with networking and see if you get the same error

Ok, lets try and lay out what is happening, you have your home computer sitting in the DMZ at your house. the IP for this is what(internet capable or local Lan)? you said you have your DNS hosted at go daddy, it is redirection to your internet IP that is hosted on your router? can you ping that url and get a response? what are your power settings set to in vista? have you checked to see if it is setup to sleep or power down components to save power?

Haven't used any linux servers with vista yet, might try in awhile but isn't a configuration that we use often

basically it comes down to any machine that connect to the server will need to have CAl, just comes down to what kind you will need. if you have several machines that are just kiosik machines a Device CAL will allow anyone to use that machine without issue, this would probably what you are looking for. one CAL per device or user (in your case with the kosik machines a per device would work better)

Licensing overiew for Server 2003 Changes in Use Rights for Windows Server 2003 Microsoft is pleased to introduce new licensing options to address customer business needs and to complement the technical capabilities of our Windows Server 2003 products. This is part of a broad effort to improve the customer experience with licensing Microsoft software and our ongoing effort to make licensing more consistent, predictable, and flexible for our customers. These new options are designed to provide customers with an enhanced ability to license Microsoft server products in a consistent manner across our product line. The new options will be particularly beneficial to those who seek user-based licensing, those who would like to provide server access to their end-customers or partners, or those who run solutions that leverage multiple Microsoft server products. These changes to the Microsoft licensing program will first be available with the Microsoft Windows Server 2003 product release. Top of page The Windows Server Licensing Model—Elements That Have Not Changed Although there have been changes to the Windows Server 2003 licensing model, the following elements have not changed: • Every installed copy of the server software requires the purchase of a Windows server license. • A Windows Server 2003 Client Access License (Windows CAL) is required in order to access or use the server software. • A Windows CAL is not required if access to the server software is via the Internet and is "unauthenticated"—for example, accessing a Web site for general information where no identifying credentials are exchanged. • A Terminal Server Client Access License (TS CAL) is required for Standard Edition and Enterprise Edition to use Terminal Server or otherwise host a remote graphical user interface (GUI) session, except for a console session. In Windows 2000, there was an exception to this licensing requirement and that will change with this release, as outlined below. • A Terminal Server Client Access License (TS CAL) is required to use Terminal Server or otherwise host a remote graphical user interface (GUI) session, except for a console session. In Windows 2000, there was an exception to this licensing requirement and that will change with this release, as outlined below. • A Datacenter Terminal Server Client Access License (TS CAL) is required for Datacenter Edition to use Terminal Server or otherwise host a remote graphical user interface (GUI) session, except for a console session. Top of page Changes to Windows Server 2003 Licensing The following reflects changes to the Windows Server 2003 licensing requirements: • New user-based CAL. Microsoft is introducing a new type of Windows CAL. In addition to existing device-based CALs (Device CAL), a user-based CAL (User CAL) will be available for purchase. You can choose to purchase a Windows Device CAL for every device accessing your servers, or you can purchase a Windows User CAL for every named user accessing your servers. By having two types of Windows CALs, you are able to use the model that makes sense for your organization. For example, purchasing a Windows User CAL might make more sense if your company has a need for employees to have roaming access using multiple devices. Windows Device CALs may make more sense if your company has multiple-shift workers who share devices. Similarly, Terminal Server (TS) will offer both device-based and user-based CALs: TS Device CAL and TS User CAL. • New name for Per Seat licensing mode and expanded usage right. The two CAL licensing modes that exist in Windows 2000 Server still exist, but one of the modes has a new name: The Per Seat mode has been changed to the "Per Device or Per User" mode, and Windows User CALs can be applied. The name of the Per Server mode has not changed, and the rights associated with each of the modes have essentially not changed. Per Device or Per User mode is concerned with the total number of devices or users (or a combination of devices and users) accessing the server software across any number of servers, at any time. In this mode, you need a Windows CAL for every device or user that will be accessing Windows Server. In Per Device or Per User mode, only one Windows CAL is needed for any given device or user to access Windows Server, regardless of which servers it is accessing. Per Server mode is concerned with the number of concurrent connections to the server software. You need to purchase Windows CALs for the maximum number of simultaneous connections to that server. Any device or user can access the server, but the number of simultaneous access connections hitting the server at any given time must not exceed the number of Windows CALs designated to that server. • New External Connector License option. The new External Connector license (EC) can be purchased to enable access to your servers instead of buying individual Windows CALs for external users (or their devices). The EC license is purchased for every copy of the Windows server software that is accessible to the external user. An example of an external user is a person who is not an employee or similar personnel of the company or its affiliates. Terminal Server will also introduce an EC license—the Terminal Server External Connector (TS-EC)—to address a similar need: to enable external users to access a company's terminal servers, without the need to purchase individual TS CALs for them or their devices.

no, they would have to go to dedicated boxes, the way SBS has exchange intergrated you can't move it to another machine. you would have to upgarde the SBS to dedicated boxes then you would be fine