0

I have tried to configure alternate access mappings in my SharePoint 2010 which is installed in WorkGroup Windows Server 2008 R2 server but could not make it work. Here are my steps.

  1. Go to Central Administration-> Manage Web Application.
  2. Select a web application and extend it.
  3. Provide the my12server.com in the host header and leave other default values as it is. I changed the zone to Extranet.
  4. Click Ok.
  5. After sometime, it creates Web Application in SharePoint and Web Site in IIS.
  6. I have changed my hosts file by adding entry 192.168.1.11 my12server.com
  7. Browse the new extended. It asks for credential. Supplied the correct credential but nothing got display. Just a blank page.

Note: I have however successfully extended web application when the SharePoint 2010 is in domain machine.

Please advice me.

Thanks Prakash

Charles
  • 50,943
  • 13
  • 104
  • 142
Prakash
  • 422
  • 1
  • 12
  • 31

1 Answers1

0

SharePoint is designed to work in domain environments only. In other words, you cannot expect to run it on an underlying Windows Server which joined into a workgroup and expect full functionality. Although there are blog posts around describing installation in a workgroup environment (or, better to say, using local accounts), I wouldn't recommend wasting time with such a mode of operation.

Furthermore, it doesn't make sense to extend a web application just for the sake of providing another hostname. Extending web applications multiple times is mostly useful when you need different authentication providers for each of them. In your simple case you can just configure multiple Alternate Access Mapping records for a single web application.

Ondrej Tucny
  • 27,626
  • 6
  • 70
  • 90
  • Why not? I think this mode of operation makes perfect sense in a development setting. – Ytrog Dec 11 '13 at 11:28
  • @Ytrog Well, yes, it does make sense for development scenarios, but for limited ones only. You just cannot exploit all options SharePoint gives you when you run it on a non-domain-joined server. That's the way the cookie crumbles. So making perfect sense != working or possible. In SP2007 it was almost always possible, in SP2010 it's possible for basic scenarios, and in SP2013 it's barely possible in common scenarios. Currently, in my company we run all development machines in a dedicated dev domain. – Ondrej Tucny Dec 11 '13 at 13:19