I have two questions...
Could I create a complete portal for Internet with WSS 3.0 or MOSS is necessary for that?
I wanted to know if it is possible to install WSS 3.0 on Windows Server 2008 R2 or Windows Server 2003 is the only possibility for this version of Sharepoint.
The answer to your first question really depends on your definition of portal and how broad it is. It is possible to have an efficient intranet solution with WSS without full blown SharePoint. Microsoft offers a lot of templates too, for specific site types.
To your second question, yes you can install WSS 3.0 on 2008 R2, but you will need to apply the latest service packs.
Related
We have a classic ASP application we just migrated from Windows 2008 R2 to Windows 2012 R2 Core.
Apparently Core versions of windows don't include cdosys or cdonts and thus our application can no longer send email.
Most of the advice I can find suggests using system.net.mail for sending email which of course is a .NET technology and we're using classic ASP.
We do have .NET on our system but I'm not sure if classic ASP could talk to a .NET page for sending email?
Besides using a 3rd party COM utility like Persits ASPEmail are there any native ways of working around this?
We do NOT want to convert the server core instance to the full version of windows. That's killing an ant with a bazooka. This is only impacting two places in our code and everything else works just fine on core.
Unfortunately, CDONTS was superseded by CDOSYS some time ago. When migrating from Windows Server 2008 to Windows Server 2012 I had this exact same issue, but managed to find a fix.
It involves taking a copy of the cdonts.dll file from the Windows Server 2008 Server and adding it to the Windows Server 2012 server then registering it with the relevant COM subsystem without any need to change code or install a 3rd Party library.
Hopefully the same method will work with Core but I haven't tested it.
Does anybody know how to get export to XLSX support for SQL Server 2008 R2 Reporting Services without upgrading to SQL Server 2012 or using any 3rd party tools?
Apart from developing your own render? Nope. I haven't been able to find ANY information on that by the way.
Apart from going to SQL Server 2012 (a 3rd party renderer may be more cost effective) you could develop your own ASP.Net app while using EPPlus that would link from the report. This stackoverflow post may help start you off with the code.
Can both clients be installed and used at the same time ?
The purpose of using both is based needs to develop for Lync 2010 while still using Communicator 2007 in a corporate environment. Or would a developer be forced to have two different machines/VMs/boot environments ?
No - you can't run both side-by-side. Installing Lync will uninstall Communicator.
However, you can use a registry hack (unsupported, unfortunately) to enable your copy of Lync to run against your OCS infrastructure. This works for R2, not 100% sure about R1.
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator]"DisableServerCheck"=dword:00000001
If you're serious about Lync development, the best solution is to build a server environment specifically for developing against.
Trying to develop and test an ASP.NET MVC 2 as well as a hosted WCF app where the client is limited to IIS 6.0 (OS Windows 2003). I am developing and testing in Windows 7 which has IIS 7. I do not have access to a Windows 2003 disk, so creating a VM doesn't appear to be a viable option for me...
Any suggestions or tips would be greatly appreciated
Update:
Lucas' response led me to consider a virtual dedicated server... Going to try that for a testing environment.
You don't have many options
You bend (get a MSDN subscription or Win 2k3)
Your client bends (upgrades to Win7/2k8)
Find someone you know who can let you use an IIS 6 machine.
Get your client to let you use one of their machines during development
You can virtual PC it. If you can use Windows XP, M$ provides a virtual machine + WinXP trial. It's more for using IE6 I think, but I don't think it limits application installation like IIS.
I don't have the link anymore, but it's provided by M$ from their download area
I'm looking for a way to programatically change features ("Programs and Features" -> "Turn Windows Features on or off") in Windows Vista (and newer Redmond OS, e.g. Server 2008).
Ideal solution would be in the form of a Powershell script (Get-Features, Set-Features), however any pointers to MSDN/other documentation would be very welcome! (my initial quick Google/StackOverflow search came up empty).
Having an automatic way to turn features on or off would allow me to automate computer setup for different scenarios. For example, to develop ASP.NET applications using IIS a bunch of IIS features need to be installed that are not installed by default. My current process of "make sure at least the features shown in this screenshot are checked" leaves a lot to be desired.
I just found an extension that works for Windows 7. "PowerShell module to Add/Remove Windows 7 features" - https://psclientmanager.codeplex.com/
in windows server 2008, there is the ServerManagerCmd command. This can install IIS with or without the subfeatures you want. You can also install/uninstall most of the major Windows features.
You can setup your server the way you want then run ServerManagerCmd -query template.xml. This exports the configuration to an Xml file.
You need to transform the file to prepare it for use on other servers
Copy the transformed file to the server you want to configure and run ServerManagerCmd -inputPath transformTemplate.xml
The way to do this in Vista and Windows 2008 is with the PKGMGR command line tool. Search MSDN for this tool to find a list of features/packages.
It looks live Powershell V2 on Server 2008 R2 (Beta) has a module that does exactly this. Let's hope Windows 7 will have this functionality as well...
For more details, see Managing Server Features with PowerShell Cmdlets on Windows 2008 Server R2 Beta
There's unfortunately not a set of cmdlets, yet, nor is there anything in WMI or any other easily-accessible area. Interestingly, Server Core's script-based role management features will only work on Server Core :). Windows 7 may bring some relief in this regard - but it also might not. In the meantime, you're pretty much left with the native Win32 APIs mentioned in the other answer.
As an aside, I should point out that MS deliberately doesn't want applications installing major OS features due to the security considerations. Adding IIS isn't something done lightly, and it brings with it security considerations and responsibilities. Witness MS' own application setups, which check for pre-reqs like that, but do not offer to install them for you. While I understand wanting to make your app setup as painless as possible, there's also damage to be done in putting major functionality into the OS under someone's nose :). I personally would prefer that apps err on the side of caution, tell me what they need, and let me make the decisions about how and what to install things - especially major functionality that will open ports and be able to execute arbitrary code, like IIS.