RE: .net questions
Yea. I had the exact same issue -Original Message- From: Benjamin Zachary [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 10:06 PM To: MS-Exchange Admin Issues Subject: RE: .net questions I thought that's what you meant, I have 3602, but I knew you had the newer one and mine was 06. heeh .. Siegfried - A bunch of us went through this before, and I know some people said there's works, but mine never worked, with or without a domain or AD. I even tried joining the domain from an xp box and then doing it, I got an error every time. Being fairly proficient in RDP TS (manage about 12 servers @ 250 users) I felt I had it all setup correctly just for a basic connection from an admin acct. Oh well, looking forward to the new build.. -Original Message- From: William Lefkovics [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 9:27 PM To: MS-Exchange Admin Issues Subject: RE: .net questions Oops... Yes, 3628 not 3268. Thanks. -Original Message- From: Siegfried Weber [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 6:02 PM To: MS-Exchange Admin Issues Subject: RE: .net questions Not William but going to reply inline... -Original Message- I'm running 3206 in a test environment and its running okay. Found out the hard way that e2k doesn't work on it and the RDP5.1 isn't implemented correctly. (Cant connect to it via WinXP using rdp5.1). I'd double check your config then. I've been using Win.NET Server since 3604 and am now running 3628 and I never had any issues using Win.XP to connect via RDP to the Win.NET box. oh yah and the new sharepoint on it is much nicer. I assume you refer to Sharepoint Team Services which are removed in later builds. Hey William is that new build on the msdn? I didn't see it .. Nope. Build 3628 (which William I believe refers to) is only for beta testers. Cheers:Siegfried runat=server / List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: .net questions
Really weird. I've 10 servers (one is a .NET Server) and two Win.XP plus one Win.2k WS and all don't have any issues connection via RDP to each other. I can manage the Win.2k server from Win.XP as well as the Win.NET server from Win.2k or Win.XP. Note that I am not using the built-in Win.2k Terminal Client stuff but rather installed the TSAC MMC snapin plus the Win.XK Remote Desktop client on all my Win.2k machines (server and WS) because I like those two more ;-) Cheers:Siegfried runat=server / -Original Message- From: Benjamin Zachary [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 03, 2002 7:06 AM To: MS-Exchange Admin Issues Subject: RE: .net questions I thought that's what you meant, I have 3602, but I knew you had the newer one and mine was 06. heeh .. Siegfried - A bunch of us went through this before, and I know some people said there's works, but mine never worked, with or without a domain or AD. I even tried joining the domain from an xp box and then doing it, I got an error every time. Being fairly proficient in RDP TS (manage about 12 servers @ 250 users) I felt I had it all setup correctly just for a basic connection from an admin acct. Oh well, looking forward to the new build.. -Original Message- From: William Lefkovics [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 9:27 PM To: MS-Exchange Admin Issues Subject: RE: .net questions Oops... Yes, 3628 not 3268. Thanks. -Original Message- From: Siegfried Weber [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 6:02 PM To: MS-Exchange Admin Issues Subject: RE: .net questions Not William but going to reply inline... -Original Message- I'm running 3206 in a test environment and its running okay. Found out the hard way that e2k doesn't work on it and the RDP5.1 isn't implemented correctly. (Cant connect to it via WinXP using rdp5.1). I'd double check your config then. I've been using Win.NET Server since 3604 and am now running 3628 and I never had any issues using Win.XP to connect via RDP to the Win.NET box. oh yah and the new sharepoint on it is much nicer. I assume you refer to Sharepoint Team Services which are removed in later builds. Hey William is that new build on the msdn? I didn't see it .. Nope. Build 3628 (which William I believe refers to) is only for beta testers. Cheers:Siegfried runat=server / List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
.net questions
Situation: Our web committie (i am not involved) meet and decided there was no need to go to .net for web at this time, becuase they could do everything they needed to with out it. not that great, can do the same stuff myself no-tech manager a then went to non-tech higher up b (my boss's boss) and said what! we need to go to .net, as MS says it is the next best thing! non-tech higher up b (my boss's boss) said to my boss what is up with .net and why aren't we going to it? MS is advertizing it all over the place! we need to get it! my boss said - Find OUT what is going on! I went to technet and MS and now the lists. Per MS it is a XML web serivce which somehow has serversMS site was not clear on how it worked. The Technet article were better on told me that .net is a programming framework to link web and traditional server systems together to enable better flow of information. Am I correct in my undertsanding? Is .net server a true NOS based or is is just web services? My undertanding is that it is not offically released yet, is that correct? Is anyone beta testing it? If so what problems have they found with Exchange and Terminal services? I thought I read from one of my lists that there were issues with exchange?? Who is planning on going to it? Thanks For Your Help. Elizabeth Thompson Service and Support Tech CCBC - Catonsville List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: .net questions
Funny, just got out of a meeting with MS about .net. I would suggest getting your MS rep out there to the developers and infrastructure groups to see what .net provides for both areas. Your basically looking at XML Web Services that will allow you Rapid Application Development and cross platform communication. There are four parts to .net: Clients, Servers, XML Web Services and Developer tools We just got the developer pitch today (kind of understood what was going on) and will get the infrastructure part later (my area). But .net as far as I can figure is a family of development and server products. Exchange 2000 is one of the .net applications but I don't think Terminal Services really changes much between Win2K and .net servers. Biztalk Server, Share Point Portal Server, Exchange 2000, SQL 2000, etc. are all part of the 12 server products that will be available. There are also the development platforms Visual Studio .net, etc. Ken --- Ken Leyba Windows/Exchange System Administrator California State University Dominguez Hills -Original Message- From: Thompson, Elizabeth [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 5:00 PM To: MS-Exchange Admin Issues Subject: .net questions Situation: Our web committie (i am not involved) meet and decided there was no need to go to .net for web at this time, becuase they could do everything they needed to with out it. not that great, can do the same stuff myself no-tech manager a then went to non-tech higher up b (my boss's boss) and said what! we need to go to .net, as MS says it is the next best thing! non-tech higher up b (my boss's boss) said to my boss what is up with .net and why aren't we going to it? MS is advertizing it all over the place! we need to get it! my boss said - Find OUT what is going on! I went to technet and MS and now the lists. Per MS it is a XML web serivce which somehow has serversMS site was not clear on how it worked. The Technet article were better on told me that .net is a programming framework to link web and traditional server systems together to enable better flow of information. Am I correct in my undertsanding? Is .net server a true NOS based or is is just web services? My undertanding is that it is not offically released yet, is that correct? Is anyone beta testing it? If so what problems have they found with Exchange and Terminal services? I thought I read from one of my lists that there were issues with exchange?? Who is planning on going to it? Thanks For Your Help. Elizabeth Thompson Service and Support Tech CCBC - Catonsville List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: .net questions
It sounds like what her group was discussing was the .NET development platform (ASPX, C#, VB.NET, etc). At this time, its easy to confuse the two (dev vs. server). Frankly, I left it up to our developers to decide. All they needed from me was to upgrade the MDAC and install .NET Framework on the servers -Original Message- From: Ken Leyba [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 5:14 PM To: MS-Exchange Admin Issues Subject: RE: .net questions Funny, just got out of a meeting with MS about .net. I would suggest getting your MS rep out there to the developers and infrastructure groups to see what .net provides for both areas. Your basically looking at XML Web Services that will allow you Rapid Application Development and cross platform communication. There are four parts to .net: Clients, Servers, XML Web Services and Developer tools We just got the developer pitch today (kind of understood what was going on) and will get the infrastructure part later (my area). But .net as far as I can figure is a family of development and server products. Exchange 2000 is one of the .net applications but I don't think Terminal Services really changes much between Win2K and .net servers. Biztalk Server, Share Point Portal Server, Exchange 2000, SQL 2000, etc. are all part of the 12 server products that will be available. There are also the development platforms Visual Studio .net, etc. Ken --- Ken Leyba Windows/Exchange System Administrator California State University Dominguez Hills -Original Message- From: Thompson, Elizabeth [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 5:00 PM To: MS-Exchange Admin Issues Subject: .net questions Situation: Our web committie (i am not involved) meet and decided there was no need to go to .net for web at this time, becuase they could do everything they needed to with out it. not that great, can do the same stuff myself no-tech manager a then went to non-tech higher up b (my boss's boss) and said what! we need to go to .net, as MS says it is the next best thing! non-tech higher up b (my boss's boss) said to my boss what is up with .net and why aren't we going to it? MS is advertizing it all over the place! we need to get it! my boss said - Find OUT what is going on! I went to technet and MS and now the lists. Per MS it is a XML web serivce which somehow has serversMS site was not clear on how it worked. The Technet article were better on told me that .net is a programming framework to link web and traditional server systems together to enable better flow of information. Am I correct in my undertsanding? Is .net server a true NOS based or is is just web services? My undertanding is that it is not offically released yet, is that correct? Is anyone beta testing it? If so what problems have they found with Exchange and Terminal services? I thought I read from one of my lists that there were issues with exchange?? Who is planning on going to it? Thanks For Your Help. Elizabeth Thompson Service and Support Tech CCBC - Catonsville List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: .net questions
I run a Windows.Net Active Directory domain with beta3 release 3268. And on a dev box I have VisualStudio.Net. .Net is both a development platform and a name given the next version of Windows. William -Original Message- From: Thompson, Elizabeth [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 5:00 PM To: MS-Exchange Admin Issues Subject: .net questions Situation: Our web committie (i am not involved) meet and decided there was no need to go to .net for web at this time, becuase they could do everything they needed to with out it. not that great, can do the same stuff myself no-tech manager a then went to non-tech higher up b (my boss's boss) and said what! we need to go to .net, as MS says it is the next best thing! non-tech higher up b (my boss's boss) said to my boss what is up with .net and why aren't we going to it? MS is advertizing it all over the place! we need to get it! my boss said - Find OUT what is going on! I went to technet and MS and now the lists. Per MS it is a XML web serivce which somehow has serversMS site was not clear on how it worked. The Technet article were better on told me that .net is a programming framework to link web and traditional server systems together to enable better flow of information. Am I correct in my undertsanding? Is .net server a true NOS based or is is just web services? My undertanding is that it is not offically released yet, is that correct? Is anyone beta testing it? If so what problems have they found with Exchange and Terminal services? I thought I read from one of my lists that there were issues with exchange?? Who is planning on going to it? Thanks For Your Help. Elizabeth Thompson Service and Support Tech CCBC - Catonsville List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: .net questions
Try this link for some pretty fair information: http://arstechnica.com/paedia/n/net/net-1.html | -Original Message- | From: Thompson, Elizabeth [mailto:[EMAIL PROTECTED]] | Sent: Tuesday, July 02, 2002 17:00 | To: MS-Exchange Admin Issues | Subject: .net questions | | | Situation: | | Our web committie (i am not involved) meet and decided there | was no need to | go to .net for web at this time, becuase they could do everything they | needed to with out it. not that great, can do the same stuff myself | | no-tech manager a then went to non-tech higher up b (my | boss's boss) and | said what! we need to go to .net, as MS says it is the next | best thing! | | non-tech higher up b (my boss's boss) said to my boss what | is up with | .net and why aren't we going to it? MS is advertizing it all | over the place! | we need to get it! | | my boss said - Find OUT what is going on! | | I went to technet and MS and now the lists. | | Per MS it is a XML web serivce which somehow has | serversMS site was not | clear on how it worked. The Technet article were better on | told me that .net | is a programming framework to link web and traditional | server systems | together to enable better flow of information. | | Am I correct in my undertsanding? | | Is .net server a true NOS based or is is just web services? | | My undertanding is that it is not offically released yet, is | that correct? | | Is anyone beta testing it? If so what problems have they | found with Exchange | and Terminal services? I thought I read from one of my lists | that there were | issues with exchange?? | | | Who is planning on going to it? | | | Thanks For Your Help. | | Elizabeth Thompson | Service and Support Tech | CCBC - Catonsville | | List Charter and FAQ at: | http://www.sunbelt-software.com/exchange_list_charter.htm | | List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: .net questions
I'm running 3206 in a test environment and its running okay. Found out the hard way that e2k doesn't work on it, and the RDP5.1 isn't implemented correctly. (Cant connect to it via WinXP using rdp5.1). The server has 3 version on it, standard server, web server, and enterprise server if I remember correctly. The web server had everything web on it, for add/remove users and basically all admin tools were in the browser (like the admin web site, but much more). The other two seem to run pretty nice. Our 3206 is running AD , DNS, DHCP, and PoP3 mail services, oh yah and the new sharepoint on it is much nicer. Hey William is that new build on the msdn? I didn't see it .. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: .net questions
Not William but going to reply inline... -Original Message- I'm running 3206 in a test environment and its running okay. Found out the hard way that e2k doesn't work on it and the RDP5.1 isn't implemented correctly. (Cant connect to it via WinXP using rdp5.1). I'd double check your config then. I've been using Win.NET Server since 3604 and am now running 3628 and I never had any issues using Win.XP to connect via RDP to the Win.NET box. oh yah and the new sharepoint on it is much nicer. I assume you refer to Sharepoint Team Services which are removed in later builds. Hey William is that new build on the msdn? I didn't see it .. Nope. Build 3628 (which William I believe refers to) is only for beta testers. Cheers:Siegfried runat=server / List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
Re: .net questions
On Tue, 2 Jul 2002, at 8:00pm, Thompson, Elizabeth wrote: Is .net server a true NOS based or is is just web services? .NET has at least two meanings: In one sense, .NET is just the latest thing Microsoft is using instead of a version number. We had Windows 95, 98, 2000, ME, XP, and now .NET. Likewise Office, SQL Server, Exchange, and so on. Ho-hum, marketing strikes again. In another sense, .NET is a software environment. .NET combines a number of tools and technologies to give developers an application framework to develop software in, and users to run it in. Microsoft says it will let you develop software faster, make it run better, eliminate backwards compatibility problems, make everything platform independent, and create world peace. ;-) I expect reality to be something less then that. The two means of .NET do not necessarily have anything to do with each other. Sure, Windows.NET is supposed to be Windows re-implemented on .NET, but software release schedules being what they are, it would not surprise me to see that pushed off into the next release. :) -- Ben Scott [EMAIL PROTECTED] | The opinions expressed in this message are those of the author and do not | | necessarily represent the views or policy of any other person, entity or | | organization. All information is provided without warranty of any kind. | List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: .net questions
Note that Windows XP and Windows.NET will coexist for quite some time. Windows XP = Client OS Windows.NET = Server OS Cheers:Siegfried runat=server / -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 03, 2002 3:20 AM To: MS-Exchange Admin Issues Subject: Re: .net questions On Tue, 2 Jul 2002, at 8:00pm, Thompson, Elizabeth wrote: Is .net server a true NOS based or is is just web services? .NET has at least two meanings: In one sense, .NET is just the latest thing Microsoft is using instead of a version number. We had Windows 95, 98, 2000, ME, XP, and now .NET. Likewise Office, SQL Server, Exchange, and so on. Ho-hum, marketing strikes again. In another sense, .NET is a software environment. .NET combines a number of tools and technologies to give developers an application framework to develop software in, and users to run it in. Microsoft says it will let you develop software faster, make it run better, eliminate backwards compatibility problems, make everything platform independent, and create world peace. ;-) I expect reality to be something less then that. The two means of .NET do not necessarily have anything to do with each other. Sure, Windows.NET is supposed to be Windows re-implemented on .NET, but software release schedules being what they are, it would not surprise me to see that pushed off into the next release. :) -- Ben Scott [EMAIL PROTECTED] | The opinions expressed in this message are those of the author and do not | | necessarily represent the views or policy of any other person, entity or | | organization. All information is provided without warranty of any kind. | List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: .net questions
Oops... Yes, 3628 not 3268. Thanks. -Original Message- From: Siegfried Weber [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 6:02 PM To: MS-Exchange Admin Issues Subject: RE: .net questions Not William but going to reply inline... -Original Message- I'm running 3206 in a test environment and its running okay. Found out the hard way that e2k doesn't work on it and the RDP5.1 isn't implemented correctly. (Cant connect to it via WinXP using rdp5.1). I'd double check your config then. I've been using Win.NET Server since 3604 and am now running 3628 and I never had any issues using Win.XP to connect via RDP to the Win.NET box. oh yah and the new sharepoint on it is much nicer. I assume you refer to Sharepoint Team Services which are removed in later builds. Hey William is that new build on the msdn? I didn't see it .. Nope. Build 3628 (which William I believe refers to) is only for beta testers. Cheers:Siegfried runat=server / List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: .net questions
I thought that's what you meant, I have 3602, but I knew you had the newer one and mine was 06. heeh .. Siegfried - A bunch of us went through this before, and I know some people said there's works, but mine never worked, with or without a domain or AD. I even tried joining the domain from an xp box and then doing it, I got an error every time. Being fairly proficient in RDP TS (manage about 12 servers @ 250 users) I felt I had it all setup correctly just for a basic connection from an admin acct. Oh well, looking forward to the new build.. -Original Message- From: William Lefkovics [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 9:27 PM To: MS-Exchange Admin Issues Subject: RE: .net questions Oops... Yes, 3628 not 3268. Thanks. -Original Message- From: Siegfried Weber [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 02, 2002 6:02 PM To: MS-Exchange Admin Issues Subject: RE: .net questions Not William but going to reply inline... -Original Message- I'm running 3206 in a test environment and its running okay. Found out the hard way that e2k doesn't work on it and the RDP5.1 isn't implemented correctly. (Cant connect to it via WinXP using rdp5.1). I'd double check your config then. I've been using Win.NET Server since 3604 and am now running 3628 and I never had any issues using Win.XP to connect via RDP to the Win.NET box. oh yah and the new sharepoint on it is much nicer. I assume you refer to Sharepoint Team Services which are removed in later builds. Hey William is that new build on the msdn? I didn't see it .. Nope. Build 3628 (which William I believe refers to) is only for beta testers. Cheers:Siegfried runat=server / List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
