Wireless SSID @ Multiple Sites

Not sure where to post this , but here goes.
I have 8 sites all running Motorola Wireless Controllers with multipe SSID's.
I have recently decided to move to the Cisco 2504 WLC since our Motorola devices were out of warrnaty and support.
The issue I am experiencing is when I configure my WLC 2504 with the identicle SSID parameters\settings as my Motorola
devices the users are unable to connect. They have to manually remove the existing wireless profile and re-create it.
This will be a bit of a pain especially with 700 users.
Any ideas if such a feature can enable this "talk nice" piece.
Cheers and hopfully this makes sense.

Ooops wrong WLAN.
WLAN Identifier.................................. 5
Profile Name..................................... PDA
Network Name (SSID).............................. GLPDABG
Status........................................... Enabled
MAC Filtering.................................... Disabled
Broadcast SSID................................... Enabled
AAA Policy Override.............................. Enabled
Network Admission Control
  Client Profiling Status ....................... Disabled
   DHCP ......................................... Disabled
   HTTP ......................................... Disabled
  Radius-NAC State............................... Disabled
  SNMP-NAC State................................. Disabled
  Quarantine VLAN................................ 0
Maximum number of Associated Clients............. 0
Maximum number of Clients per AP Radio........... 200
Number of Active Clients......................... 1
Exclusionlist.................................... Disabled
Session Timeout.................................. 1800 seconds
User Idle Timeout................................ 300 seconds
--More or (q)uit current module or to abort
User Idle Threshold.............................. 0 Bytes
NAS-identifier................................... CS-2504-01
CHD per WLAN..................................... Enabled
Webauth DHCP exclusion........................... Disabled
Interface........................................ wifibg
Multicast Interface.............................. Not Configured
WLAN IPv4 ACL.................................... unconfigured
WLAN IPv6 ACL.................................... unconfigured
mDNS Status...................................... Enabled
mDNS Profile Name................................ default-mdns-profile
DHCP Server...................................... Default
DHCP Address Assignment Required................. Disabled
Static IP client tunneling....................... Disabled
Quality of Service............................... Silver
Per-SSID Rate Limits............................. Upstream      Downstream
Average Data Rate................................   0             0
Average Realtime Data Rate.......................   0             0
Burst Data Rate..................................   0             0
Burst Realtime Data Rate.........................   0             0
Per-Client Rate Limits........................... Upstream      Downstream
Average Data Rate................................   0             0
Average Realtime Data Rate.......................   0             0
Burst Data Rate..................................   0             0
--More or (q)uit current module or to abort
Burst Realtime Data Rate.........................   0             0
Scan Defer Priority.............................. 4,5,6
Scan Defer Time.................................. 100 milliseconds
WMM.............................................. Allowed
WMM UAPSD Compliant Client Support............... Disabled
Media Stream Multicast-direct.................... Disabled
CCX - AironetIe Support.......................... Enabled
CCX - Gratuitous ProbeResponse (GPR)............. Disabled
CCX - Diagnostics Channel Capability............. Disabled
Dot11-Phone Mode (7920).......................... Disabled
Wired Protocol................................... None
Passive Client Feature........................... Disabled
Peer-to-Peer Blocking Action..................... Disabled
Radio Policy..................................... 802.11b and 802.11g only
DTIM period for 802.11a radio.................... 1
DTIM period for 802.11b radio.................... 1
Radius Servers
   Authentication................................ Global Servers
   Accounting.................................... Global Servers
      Interim Update............................. Disabled
   Dynamic Interface............................. Disabled
   Dynamic Interface Priority.................... wlan
Local EAP Authentication......................... Disabled
--More or (q)uit current module or to abort
Security
   802.11 Authentication:........................ Open System
   FT Support.................................... Disabled
   Static WEP Keys............................... Disabled
   802.1X........................................ Disabled
   Wi-Fi Protected Access (WPA/WPA2)............. Enabled
      WPA (SSN IE)............................... Disabled
      WPA2 (RSN IE).............................. Enabled
         TKIP Cipher............................. Disabled
         AES Cipher.............................. Enabled
                                                               Auth Key Management
         802.1x.................................. Disabled
         PSK..................................... Enabled
         CCKM.................................... Disabled
         FT-1X(802.11r).......................... Disabled
         FT-PSK(802.11r)......................... Disabled
         PMF-1X(802.11w)......................... Disabled
         PMF-PSK(802.11w)........................ Disabled
      FT Reassociation Timeout................... 20
      FT Over-The-DS mode........................ Enabled
      GTK Randomization.......................... Disabled
      SKC Cache Support.......................... Disabled
--More or (q)uit current module or to abort
      CCKM TSF Tolerance......................... 1000
   WAPI.......................................... Disabled
   Wi-Fi Direct policy configured................ Disabled
   EAP-Passthrough............................... Disabled
   CKIP ......................................... Disabled
   Web Based Authentication...................... Disabled
   Web-Passthrough............................... Disabled
   Conditional Web Redirect...................... Disabled
   Splash-Page Web Redirect...................... Disabled
   Auto Anchor................................... Disabled
   FlexConnect Local Switching................... Disabled
   flexconnect Central Dhcp Flag................. Disabled
   flexconnect nat-pat Flag...................... Disabled
   flexconnect Dns Override Flag................. Disabled
   FlexConnect Vlan based Central Switching ..... Disabled
   FlexConnect Local Authentication.............. Disabled
   FlexConnect Learn IP Address.................. Enabled
   Client MFP.................................... Optional
   PMF........................................... Disabled
   PMF Association Comeback Time................. 1
   PMF SA Query RetryTimeout..................... 200
   Tkip MIC Countermeasure Hold-down Timer....... 60
AVC Visibilty.................................... Disabled
--More or (q)uit current module or to abort
AVC Profile Name................................. None
Flow Monitor Name................................ None
Call Snooping.................................... Disabled
Roamed Call Re-Anchor Policy..................... Disabled
SIP CAC Fail Send-486-Busy Policy................ Enabled
SIP CAC Fail Send Dis-Association Policy......... Disabled
KTS based CAC Policy............................. Disabled
Assisted Roaming Prediction Optimization......... Disabled
802.11k Neighbor List............................ Disabled
802.11k Neighbor List Dual Band.................. Disabled
Band Select...................................... Disabled
Load Balancing................................... Disabled
Multicast Buffer................................. Disabled
Mobility Anchor List
WLAN ID     IP Address            Status
802.11u........................................ Disabled
MSAP Services.................................. Disabled

Similar Messages

  • WLC 7.5 Bonjour/mDNS at multiple sites

    Hi all,
    After reviewing the mDNS/Bonjour features of WLC software 7.5 (although most applies for 7.4 as well), I am left somewhat confused.  It seems that once services are discovered, there is no way to filter them to be advertised only to the site they were discovered at.
    To simplify our environment, consider the following scenario:
    A single WISM2 controller
    A single SSID using dynamic VLANs deployed across diverse locations, with Wi-Fi mDNS discoveryeg. Site A has VLANs 11, 12, 13, Site B has VLANs 21, 22, 23
    Wired mDNS discovery at both siteseg. Site A has VLANs 101, 102, 103, Site B has VLANs 201, 202, 203
    In the instance, let's say a printer, is discovered on wired VLAN 101, and I only want to advertise it to the Site A Wi-Fi VLANs, it seems that I can't.  All VLANs that are configured to advertise the printer mDNS service records receive it, which means Site B sees the printer at Site A.
    Is there any way to achieve what I want here?  It seems a crazy limitation that I can't filter the VLANs to what advertisements they receive, considering the service provider database has the learnt VLAN information in it.
    Alex

    Scott,
         LSS doesn't support mDNS-AP, it only applies over the wireless: http://www.cisco.com/en/US/docs/wireless/controller/7.5/config_guide/b_cg75_chapter_01011.html – about halfway down under Configuring Multicast Domain Name System, it states that there is no location awareness for wired service provider devices (Apple TVs). It also states that mDNS-AP devices are considered wired – even though these devices were discovered by the APs, they don’t get filtered by LSS.
         If the Service provider is in the same wireless SSID/VLAN, you wouldn't need Bonjour Gateway.  If it's in a different wireless SSID/VLAN, but on the same AP, you'd be hairpinning traffic and doubling up wireless airtime.  LSS doesn't make much sense to me, unless I'm missing something.
         Our solution so far is to extend the wireless VLAN out to a single port on the wired network, but the AppleTV can only be plugged into that port.  It limits our user's mobility with the devices.
         I've sent this on to our Cisco reps, and they are pushing it up the chain for a feature request.
    Mark

  • Managing multiple sites in different iWeb versions - PLEASE HELP!

    apnewbie/cyclosaurus/roddy/old toad (and any others more knowledgeable than i):
    i've run into a bit of a pickle. i am hoping someone can help straighten me out. i am about to jump out of a window. here's the rundown:
    (for starters, i have a .mac account and am publishing to .mac.) i created a site in iWeb 1.1.2 on my work computer (mac book pro). worked great, really lovely. thought to myself, "hey, i'd like to create another site from home, but i don't have iWeb at home (powerbook G4) - i should buy iLife 08 so i can build these things from home and not have personal files on my work computer."
    so: i had a site that i created within 1.1.2 with files written to iDisk. i purchased iWeb 08 and would like to have another site, but this one is being created in 2.0. i also am using a personal domain name this time around bought with google apps and hosted by godaddy. i published the new work in progress for a test run and...you guessed it...my original 1.1.2 site was rewritten by the 2.0 site. and the 2.0 site comes up as the standard google search page for domains that aren't up and running. whooopsie.
    sorry for the lengthy intro, but that's the background. i guess my specific questions are:
    1) i want to be able to maintain multiple sites from iWeb 2.0...can i open my 1.1.2 domain file in 2.0 and successfully bring that site into 2.0?
    2) what is the most efficient and easiest way to get both of these sites running in 2.0? right now i have two domain files (created on two different computers).
    3) for domain management, is it best to move from the iWeb folder in my home library to different folders (one for each site, with separate domain files, and my 2.0 domain file is NOT called domain, it's the name of the site) to another location? (and of course, i will back these up just in case.) and when i want to update a site, i just open that individual domain file, right? or will these sites publish over each other?
    please help. i am at my wits end. i'm sure this is a relatviely simple issue, but i'm new to iWeb.
    thanks, thanks, thanks for your help guys.
    joojy

    joojy,
    Welcome to the forums!
    First of all, your original 1.1.2 site may not, in fact, have been overwritten. It is quite possible that the site remains in it's position on the iDisk, Web/Sites/iWeb/YourSite, but because you published to the iDisk (.Mac) from 2.0, a different index.html file has been placed in the root level Web directory which is causing the 404 error. Navigate to the directory on the iDisk, using the Go menu in Finder, and look to see what is actually there. Follow this path:
    Go/iDisk/My iDisk/Web/Sites/iWeb/YourSiteWillBeHereIfYourLuckIsGood
    If your site is there, great; if it isn't, it's not really a problem because hopefully you still have the Domain.sites file on the MacBook Pro and you can republish it if necessary. If it is there, you can modify the index.html file on the iDisk using a text editor and get your url redirected back to where it should be.
    Second, do not open your 1.1.2 Domain.sites file with 2.0 until you have a backup of this Domain file. External drives are best for this. Assuming the backup is in place, launch 2.0, choose the Domain.sites file, and click on "update". It will be updated to a Domain.sites2 file. If the site looks ok then continue on with editing/publishing.
    Skipping to question (3), by all means, abandon the default location of the Domain.sites file in the Home folder's Library and get accustomed to keeping your Domain files in their own, respective folders. When you want to open one just double-click it.
    You are going to encounter difficulties publishing multiple sites in 2.0.2, unless you keep all of the sites in a single Domain file. 2.0 is publishing to a different directory on the iDisk than 1.0; it publishes to /Web/Sites/, as opposed to /Web/Sites/iWeb/. Publishing a site from a separate Domain file erases previously published sites. I have been able to publish multiple sites, from multiple Domain.sites2 files, by mounting the iDisk and actually moving the Site folder back one level, into the root Web folder, and then publishing. When finished, I move it back again. If you have RSS feeds you will probably get a 'file in use' error. The alternative, (other than keeping all sites in a single Domain), is to publish the site to a folder and then manually drop the Site folder into the Web/Sites/ directory on the iDisk. Of course, some .Mac functions are lost when publishing this way.
    Work through this info and post back.
    -Mark

  • Azure multiple site-to-site VPNs (dynamic gateway) with Cisco ASA devices

    Hello
    I've been experimenting with moving certain on-premise servers to Azure however they would need a site-to-site VPN link to our many branch sites e.g. monitoring of nodes.
    The documentation says I need to configure a dynamic gateway to have multiple site-to-site VPNs. This is not a problem for our typical Cisco ISR's. However three of our key sites use Cisco ASA devices which are listed as 'Not Compatible' with dynamic routing.
    So I am stuck...
    What options are available to me? Is there any sort of tweak-configuration to make a Cisco ASA work with Azure and dynamic routing?
    I was hoping Azure's VPN solution would be very flexible.
    Thanks

    Hello RTF_Admin,
    1. Which is the Series of CISCO ASA device you are using?
    Thank you for your interest in Windows Azure. The Dynamic routing is not supported for the Cisco ASA family of devices.
    Unfortunately, a dynamic routing VPN gateway is required for Multi-Site VPN, VNet to VNet, and Point-to-Site.
    However, you should be able to setup a site-to-site VPN with Cisco ASA 5505 series security appliance as demonstrated in this blog:
    Step-By-Step: Create a Site-to-Site VPN between your network and Azure
    http://blogs.technet.com/b/canitpro/archive/2013/10/09/step-by-step-create-a-site-to-site-vpn-between-your-network-and-azure.aspx
    You can refer to this article for Cisco ASA templates for Static routing:
    http://msdn.microsoft.com/en-us/library/azure/dn133793.aspx
    If your requirement is only for Multi-Site VPN then there is no option but to upgrade the device as Multisite VPN requires dyanmic routing and unfortunately there is no tweak or workaround due to hardware compatibility issue.
    I hope that this information is helpful
    Thanks,
    Syed Irfan Hussain

  • AP Payment for multiple sites

    Is there a way to pay more than one site for a supplier in the same payment?

    Hello All,
    Any solution for this situation ? We are on R12 and we would like to pay single payment for multiple sites for same supplier. Anyone has any idea how do we go about this ?
    Thanks in Advance
    Dinesh
    Edited by: Dinesh Chauhan on 11-May-2010 01:15

  • Multiple Domain files, Multiple Sites, Publishing Problems

    I am frustrated beyond belief. I'm an old hand-coder, coming from BBEdit, but I've been using iWeb almost exclusively since its release, because it really is a great product for quick, easy, stylish designs.
    However.... In that year, my collection of sites has grown to 12. Discovering that iWeb becomes a major dog when dealing with that much material, I found and followed the instructions - today - to separate my sites into individual domain files, and edit them individually. iWeb is much snappier and publishing goes much more quickly.
    The problem? Well... after editing, "Publish to .Mac" rarely works. Only "Publish All to .Mac" will get the site online (something about an error with the index.html file). But "Publish All to .Mac", I've just discovered, DELETES the other websites that I have previous published. All day I've been doing updates and publishing my sites, only to discover that the uploads have all been wiped out by the most recent one!
    I'm a big enough fellow to admit that my knowledge isn't total nor perfect - so please, would someone out there with a better handle on iWeb than I (preferably someone who actually deals with multiple domain files rather than someone who thinks they can guess the problem) please clue me into how we make use of this program non-destructively?
    I suppose I could always publish everything to folders and upload it to my iDisk (which itself remains ridiculously slow after how many years now? Sheesh!), but that detracts from the elegance of the .Mac integration, the counter features, - not to mention the little fact that I'm a paying .Mac customer and this darn thing should just work, no?

    Mark:
    I was where you were also. You should give iWebSites a try. It's to iWeb what iPhoto Library Manager is to iPhoto.
    I use iWebSites to manage multiple sites.. It lets me create multiple sites and multiple domain files.
    If you have multiple sites in one domain file here's the workflow I used to split them into individual site files with iWebSites. Be sure to make a backup copy of your Domain.sites files before starting the splitting process.
    This lets me edit several sites and only republish the one I want. Just remember to put a copy of your current Domain.sites file somewhere else on your HD in case the splitting gets messed up. It went very smoothly for me and I now manage 19 or so sites.
    Do you Twango?

  • Share files over multiple sites

    Hello everybody,
    Is there a way to use a single file from multiple sites without having to maintain them twice?
    For example I want to use the same PHP-functions in two projects (include file).
    Is there a Dreamweaver-technique which allows me to use and upload a file, that is outside of the site-root-directory.
    Librarys? Templates?
    greeting

    Is there a Dreamweaver-technique
    Firstly, this has nothing to do with Dreamweaver, so no, there isn't a DW technique. This depends on your webserver and operating system.
    The solution also depends on what kind of file you are trying to share, and if the websites are on the save server. HTML/CSS can't normally access files outside the web root, so, for instance, you can't normally share a CSS file between websites (but there is a workaround using aliases). PHP files don't have this limitation, as long as they are on the same server.
    I took a quick look at the Google hosted libraries. It looks like it is all javascript. Javascript doesn't have the same limitation that PHP has. For instance, Lots of people reference a remote copy of jQuery in their web pages.
    There is a method of sharing files across servers that involves configuring the receiving server to accept the remote file. I experimented with this some years ago but can't find any info on it now. Sorry, I can't even remember what the technique was called.  It wasn't easy to get it to work with all browsers as they have different security policies.

  • Multiple sites, different computers

    I have set up multiple websites on my original iMac using iWeb08. I just purchased a MacBook Pro with iWeb09 and would like to do one of two things: 1) Manage all my sites on each computer or 2) Manage "site1" on the MBP and "sites2-4" on the iMac. I am publishing all the sites to my MobileMe account.
    It looks like I can copy my original Domain onto a USB Drive and then transfer it to the MBP and edit there. But then I need to make sure I always bring the USB drive back and forth and replace the Domain file each time before I make any changes. Sure that will work, but seems a little annoying and time consuming.
    So my question is would it be best to separate the sites into separate Domain files and load them individually from each computer? or just maintain each site on each computer? Can I even publish to MobileMe from two different places like I am thinking?
    Thanks for any input!

    Do these sites have domain names associated with them?
    If you publish multiple sites from separate domain files to the same MMe account the last published site will be the default for any domain name using the CNAME method and will be the default URL for that MMe account: http://web.me.com/YourMMe_AccountName/.
    The full URL to each site will work: http://web.me.com/YourMMe_Account_Name/SiteName.
    Are those computers linked together on a local network? If so you can just log into the primary computer which houses the domain file from the other computer and work on the domain file. Or, if you have an external HD connected to any of the computers, put the domain file on it and set up access so both computers can reach it.
    There is another possible method using DropBox: Old Toad's Tutorial #21 - Managing an iWeb site from multiple Macs with Dropbox.. It's worked for me on a simple site. But one user reported photo pages not getting updated on one computer. It does take a while for the other computer to be updated as it has to be on and connected to the internet. Just proceed with caution till you're sure there's no lagging in the updating.
    OT

  • How do you setup multiple sites to allow for code promotion?

    I am somewhat frustrated with the single site flow of the Dreamweaver Site Manager in helping me manage a full development to production code cycle.  Ideally I need to have multiple sites managed by Dreamweaver that are just different stages in the code lifecycle.  Currently DW only supports local_file -> production.  Instead I need (and this is sort of standard for software product systems) to have my local sandbox, a test site, a beta site and a production site.
    In the normal dev cycle I would work in my sandbox and have DW synchronize with my test site  ( allows scripts that need a full server to be tested in case my local machine is not running a full server ).  I can do this today with DW.  When I am ready I want be able to have DW synchronize with my beta site (might very well be on a different server via FTP) so that my users/customers can review, test and approve the changes.  When everyone has signed off I then want DW to promote this code to the production site.
    Now I can do this manually but DW seems to have 95% of the capability in place (mostly the synchronization logic).  Is there a way to have it also manage/synchronize the beta and production sites?
    Thank You

    Richmaster wrote:
    turingtest, I do have a couple questions. 
    Number one, does everyone in your family only sych their ipods from only 1 computer?  If everyone only uses itunes from 1 computer I can see how that will work.  But what if kids want to use itunes for windows?  Will "Home Sharing" allow all their music purchased on the MAC, to be also displayed on their itunes for windows laptop?  I noticed you have PCs and also an ipad.  How do you manage your family's music on these devices?
    Also, how did you first get everyone's music library into their own library?  Drag & drop?  Is the "grouping field" you mentioned under "view", then "view options"?  What does this do? 
    Thanks.
    Sorry I missed your post earlier. Normally I follow up on any replies. This one must have fallen off the page on a busy day.
    As my kids have left home I have created for them a complete clone of the familiy library, then deleted the tracks from it they don't want. Over time their libraries will divirge, but if needs be they can still update their devices using the library at home. Handy when eldest's kit was stolen.
    Grouping is just another property, useful because it isn't generally overwritten by other software but is stored in the tags, so preserved when you copy files from one place to another. You can make the column visible and edit for multiple tracks in Get Info. Some software calls the same field "mood" or "sub-genre". iTunes has a specialist purpose for it generally used with classical music, but it doesn't seem to work very well for that and I don't use it that way.
    tt2

  • Multiple sites, publish one at a time?

    I have multiple sites, but when I publish them they all publish together. Can I just publish one at a time??? If not, this program is not very good..

    I just want to select one SITE and
    upload it, not have all the others upload too. Anyway
    to get aroud that?
    It should not upload a site that has no changes. But there is no way to avoid uploading changes, unless you want to start using separate Users/username/Library/Application Support/iWeb/Domain files for each site.

  • Noob needs help with hosting multiple sites

    Hello I am new to this multi hosting. I have looked on the forum for answers but haven't found any. I am trying to figure out how to host multiple sites. I have my dns working for my default site "example1.com", but need to know if I need to add another dns record for my second site. "example2.com". Also when I point to the new fold that has the second site in it and I assign it port 82 for testing purposes I get an error message saying 403 access forbidden. I need to find out how get permission to view the site for the public. Its in a separate folder on an external hard drive right now for testing purposes. Can any body help me or point me in the right direction? Thanks so much!!!
    -Kcam1999

    {quote}
    While what you are telling him is technically functional, it is not correct
    I beg to differ, Paul. You are the one that is not correct.
    CNAMES have been deprecated as of some years ago
    What? huh? really?
    Please show me any official document that states this (and not someone who just started a rumor because he didn't understand them). Indeed, the DNS RFC makes no such claim.
    {quote}
    I stand very much corrected. CNAMEs are not officially deprecated. Interestingly, your post cites precisely what happens when CNAMES used carelessly. How many transactions are needed to resolve Apple's CNAME chain below? RFC1912 (http://www.faqs.org/rfcs/rfc1912.html) has some recommendations that suggests Apple's own network folks have, like me and perhaps even others here, some learning to do. Is that a 'best practice?'
    {quote}> Then make sure you tell Apple since this site depends on the use of CNAMEs:
    dig discussions.apple.com
    discussions.apple.com. 492 IN CNAME discussions.apple.com.edgesuite.net.
    discussions.apple.com.edgesuite.net. 4427 IN CNAME a1399.b.akamai.net.
    a1399.b.akamai.net. 2 IN A 128.241.220.82
    a1399.b.akamai.net. 2 IN A 128.241.220.72
    In fact, it uses TWO CNAMES in a chain. Oh my.{quote}
    From RFC1912 (which I'm sure many have now read here), section 2.4 is as follows:
    {quote}... having chained records such as CNAMEs pointing to CNAMEs may
    make administration issues easier, but is known to tickle bugs in
    some resolvers that fail to check loops correctly. As a result some
    hosts may not be able to resolve such names.{quote}
    {quote}> It is not valid to say "don't use these because they could cause problems'. A records can be just as problematic, as can PTRs. Let's not even talk about MX.{quote}
    How, exactly, does is an A record problematic? No chains, no additional lookups, no wasted cycles...
    We differ here -- and if we are dealing with a newbie, we don't need to enter into unnecessary complexity UNTIL it is a requirement for their solutions.
    {quote}> There are many valid reasons to use CNAMEs in DNS, not least of which is the ease of moving a service if it uses CNAMEs. For example, if you have 10 A records all pointing at the same server and you want to migrate to a different machine you have to locate and update all 10 records. If they used a CNAME to the physical server you could move them all at once using a single change. This is especially important in cross-domain links where you may not control all the origin zone files.
    {quote}
    You're somewhat reaching here, and it is well beyond the scope of the OP's post or needs (well, until they tell us more about their needs, I suppose). There is nothing difficult about 'finding' and updating the necessary records. The final example you gave is a good one and I'll say THAT is an appropriate use of a CNAME, 'though there are other workarounds for it.
    Thanks for keeping me honest.

  • Best Way to Sync Lists Across Multiple Site Collections?

    A quick query I'm hoping someone might be able to help me with...
    Within our university intranet I am assigning each department a team site within its own Site Collection. So that departments can associate Document Library files with a set list of academic courses, I created a custom dropdown field and deployed it as a Feature. While this worked within SharePoint, when you attempted to set the document properties within the Microsoft Word environment the custom fields were rendered as empty text boxes (meaning that staff are no longer restricted in when information they can enter).
    To get around this I'm considering going back-to-basics and creating a Custom List, populating it with the titles of our academic courses, and then assigning it to a Document Library via a Lookup Field. I know that Microsoft Word will then correctly display the metadata dropdown.
    As I am using multiple Site Collections, I'm unsure of the "best" way to proceed.
    I've already written a Console Application which can create a Custom List within a targetted site and populate it with the contents of an XML file - but I would need to run this every time I created a new Site Collection and what would I do when I wanted to update the contents of all the lists?
    Other than modifying my Console Application to loop through all instances of the Custom List within Site Collections and sync it to the contents of the XML file, is there another (better) option that I am over-looking?
    Its such a shame I can't create cross-collection Lookup Fields within all of the Site Collections that point to a single top-level list.
    Many thanks.

    My instinctive questions drifts towards why you have different site collections.  If all the sites were sub sites within the same site collection, a global field would solve the issue quite nicely.
    If you have legitimate reasons for keeping the sites seperated into separate site collections, I would look at using an Event Handler to trigger updates to reference values in each site collection, be they global fields or lists.  Then if you wish to update the values, you only need to update the trigger list to propagate the updates across your site sollections to all your sites in question.
    I trust that answers your question...
    Thanks
    C
    http://www.cjvandyk.com/blog

  • How to handle multiple site to site IPsec vpn on ASA, any best practice to to manage multiple ipsec vpn configrations

    how to handle multiple site to site IPsec vpn on ASA, any best practice to to manage multiple ipsec vpn configurations
    before ver 8.3 and after version 8.3 ...8.4.. 9 versions..

    Hi,
    To my understanding you should be able to attach the same cryptomap to the other "outside" interface or perhaps alternatively create a new crypto map that you attach only to your new "outside" interface.
    Also I think you will probably need to route the remote peer ip of the VPN connection towards the gateway IP address of that new "outside" and also the remote network found behind the VPN connection.
    If you attempt to use VPN Client connection instead of L2L VPN connection with the new "outside" interface then you will run into routing problems as naturally you can have 2 default routes active at the sametime (default route would be required on the new "outside" interface if VPN Client was used since you DONT KNOW where the VPN Clients are connecting to your ASA)
    Hope this helps
    - Jouni

  • Best practice for running multiple sites on 1 CF install?

    Hi-
    I'm setting up a new hosting environment (Windows Server 2008 Standard 64 bit VPS  configuration, MySQL, IIS 7, CF 9)
    Has anyone seen any docs or can anyone suggest best practices for configuring multiple sites in this environment? At this point I'm thinking simple is best, one new site in IIS for each client (domain) and point it to CF.
    Given this environment, is anyone aware of any gotchas within the setup of CF 9 on IIS 7?
    Thank you in advance,
    Rich

    There's nothing wrong with that approach. You can run as many IIS sites as you like against a single CF install.
    As for installing CF on IIS 7, I recommend that you do the following: install CF 9 without connecting it to IIS, then installing the 9.0.1 upgrade and any hotfixes, then connecting CF to IIS using the web server configuration utility. This will keep you from having to install the IIS 6 compatibility layer that's needed with CF 9 but not with CF 9.0.1.
    Dave Watts, CTO, Fig Leaf Software
    http://www.figleaf.com/
    http://training.figleaf.com/

  • Multiple Sites, Multiple Domains, one .mac account?

    So, is this possible? Can you create multiple sites in iWeb, save them to a .mac account, and then purchase domain names for each of those sites and have one assigned to each? I'm assuming no, but I'm seeing if someone knows how or someone has some workaround to keep it on .mac, but have multiple domain names for my sites?
    Thanks!!

    So, is this possible?
    No.
    Can you create multiple sites in iWeb, save them to a .mac account, and then purchase domain names for each of those sites and have one assigned to each?
    Yes and no. While .Mac does offer Domain name hosting in the form of a CNAME alias, only one Domain name is available per .Mac account. .Mac is not a registrar for multiple Domains. You can host multiple sites on your .Mac account, but if you desire a 'Domain name' for each site, you will need to purchase the Domains from a registrar like Yahoo, GoDaddy, 1&1, etc, and then forward these Domains to the appropriate sites, hosted on your .Mac account.
    I'm assuming no, but I'm seeing if someone knows how or someone has some workaround to keep it on .mac, but have multiple domain names for my sites?
    The "workaround" would be to utilize Domain forwarding from a Domain name registrar, using the .Mac urls for the forwarding address(es).
    -Mark

Maybe you are looking for