Trang web này sẽ có chức năng hạn chế trong khi chúng tôi trải qua bảo trì để cải thiện trải nghiệm của bạn. Nếu một bài viết không giải quyết được vấn đề của bạn và bạn muốn đặt câu hỏi, chúng tôi có cộng đồng hỗ trợ của chúng tôi đang chờ để giúp bạn tại @FirefoxSupport trên Twitter và /r/firefox trên Reddit.

Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

Is Thunderbird supported on Windows 2012?

  • 3 trả lời
  • 2 gặp vấn đề này
  • 16 lượt xem
  • Trả lời mới nhất được viết bởi Matt

more options

I would like to upgrade my o/s to Windows Server 2012, however I need to know that Thunderbird email client is fully compatible under Windows Server 2012? Otherwise I will stick with Windows 8.1. I just trashed my server, so I am having to reimage Windows on my Drive C:, and was considering upgrade to 2012, or stay with 8.1.

I would like to upgrade my o/s to Windows Server 2012, however I need to know that Thunderbird email client is fully compatible under Windows Server 2012? Otherwise I will stick with Windows 8.1. I just trashed my server, so I am having to reimage Windows on my Drive C:, and was considering upgrade to 2012, or stay with 8.1.

Giải pháp được chọn

Basically out of the box nothing that accesses the internet and is not "server" software will be all that easy to install on Server 2012. It's security profile is set as a server and as such simply navigating internet explorer to www.google.com will see all sorts of error messages and security warnings.

Fundamentally "under the skin" there is no difference between the operating system in server 2012 and in windows 8, except a registry Key. Just as 2003 is XP and 2008 is Vista and 2011 is Windows 7.

What this means is that software designed to run on the desktop version will run (subject to the changed role) on the server. The architecture is the same. What is fundamentally different is that a server version is optimized for different things and in this case is not a good candidate for a desktop operating system. Such things as a server has no reason to initiate connections on Ports 110 or 587, it instead expects to receive connections. So default firewall rules most likely state just that so an email program trying to get mail will not work without the firewall being adjusted first. Conversely desktop operating systems could have exactly the reverse entry. The connect to servers on those ports to get mail.

In much the same way as a church can be lived in but does not make a good home unless radically customized, Server operating systems are not a good choice for a desktop use as similar levels of customization are required for it to be comfortable in the new role.

Đọc câu trả lời này trong ngữ cảnh 👍 0

Tất cả các câu trả lời (3)

more options

The Release Notes state that only WS 2003 is supported, but I don't know if the notes are obsolete and in fact WS 2012 is compatible, or it isn't compatible, or if there's some way to make it partially compatible.

more options

Can the techies at Mozilla, jump in, and determine if Thunderbird email client will be compatible to Windows Server 2012 O/S?

Thanks,

more options

Giải pháp được chọn

Basically out of the box nothing that accesses the internet and is not "server" software will be all that easy to install on Server 2012. It's security profile is set as a server and as such simply navigating internet explorer to www.google.com will see all sorts of error messages and security warnings.

Fundamentally "under the skin" there is no difference between the operating system in server 2012 and in windows 8, except a registry Key. Just as 2003 is XP and 2008 is Vista and 2011 is Windows 7.

What this means is that software designed to run on the desktop version will run (subject to the changed role) on the server. The architecture is the same. What is fundamentally different is that a server version is optimized for different things and in this case is not a good candidate for a desktop operating system. Such things as a server has no reason to initiate connections on Ports 110 or 587, it instead expects to receive connections. So default firewall rules most likely state just that so an email program trying to get mail will not work without the firewall being adjusted first. Conversely desktop operating systems could have exactly the reverse entry. The connect to servers on those ports to get mail.

In much the same way as a church can be lived in but does not make a good home unless radically customized, Server operating systems are not a good choice for a desktop use as similar levels of customization are required for it to be comfortable in the new role.