Large outdoor /i ndoor WLAN deployment

My scenario parametres:
1. Two large (1km sq) mixed outdoor and indoor WLANs need to be deployed.
2. It's two power plants with many small and large buildings and machines indoors and out.
3. WLAN primarily to be used with Symbol handhelds in the area in conjunction with database application.
4. Location is a third world country
Given these parameters, what might you all suggest I do to maximize coverage with minimum WLAN hardware? We have several Cisco AP's already, but I am pretty sure that I will either need a lot more, or some better/more powerful antennas to get good coverage.

A proper site surveys will answer the questions you just asked...

Similar Messages

Outdoor Access Points - coverage a Large outdoor area

Hi all,
I would like a suggestion for coverage a large outdoor area. I have critical restrictions to perform any equipment deployment.
I have 2 km of radius to performe a wireless coverage, but I can put a Access Point just around the corners.Which AP and Antenna Cisco could I try to perform it?
Does Cisco have any antenna with 1 to 2 km of range ? Does any client will be can reply to this distance (1 to 2km)?
What do you think about WiMAX ?
thanks,
Murilo

You cane use Cisco Aironet 1300 Series Outdoor Access Point/Bridge:
Benefits
Industry-Leading Performance
• Data rates of 54 Mbps in the 2.4-GHz band
• Bridge range of 20 miles (32 kilometers [km]) at 11 Mbps
• Aggregate throughput approaching 28 Mbps
• Maximum transmit power of 100 milliwatts (mW) for 802.11b and 30 mW for 802.11g. Maximum power setting will vary according to individual country regulations.
Antenna Interface
• AIR-BR1310G-x-K9 or AIR-LAP1310G-x-K9: Air interface (integrated directional antenna)
• AIR-BR1310G-x-K9-R or AIR-LAP1310G-x-K9R: Two RP-TNC type connectors for external antennas
• For vehicle-installed deployments, over 100 km per hour speeds at 12 and 24 Mbps with 128-byte packets at 1 percent packet error rate (PER) (workgroup bridge mode connected to a Cisco Aironet access point or bridge)
• Support for antenna diversity
http://www.cisco.com/c/en/us/products/collateral/wireless/aironet-1300-series/product_data_sheet09186a00802252e1.html

WLAN Deployment (Assistance Needed)

Hi,
Mine is a first WLAN deployment for our new office. The hardest part is to decide which AIRONET equipment to buy and how to design.
The office has three floors plus a basement. There will be about 50 users to be connected. We shall be using 802.11n NIC. I have zeroed on AIRONET1250 AP but could not design the network to my satisfaction.
So, can anyone suggest how many AP's are needed and what additional equipment is required?? Cost is no bar but performance and high throughput is required.
Thanks
kapil

First of all, try to perform a site survey. You can survey using 802.11a and 802.11g. Once you have the coverage you want, I would agree with you with the 1252 ap's, but depending on how many ap's you require, go with a standalone wlc like the 4402-25, 4402-50, 4404-100, depending on how many ap's. Then when you have sized the wlc up, get another one for redundancy. If you really are looking for throughput, then might as well place them on a 10/100/1000 switch. The E-Series can supply power to these ap's, but it really is up to you. You can get AC adapters or even a power injector if your switch can't provide adequate power. There are very few antennas to choose from so make sure you know how these will be mounted before choosing the antennas.

Webcenter Portal large Site with Jar Files Deployment/Configuration

Hi,
I have a large WCS portal to deploy comprising of many "applications" from different groups.
Ideally we want to deploy it as a .ear file, containing menus, templates, preferences, and some other common structures.
We want to deliver each application as a .jar File. What is the best way to do it?
Can we build menus pointing to a Taskflow .jar files without incorporating the .jar in the application?
Thanks a lot,
Joao,

Thanks a lot Daniel for you prompt answer.
Do you think I can use in the default-navigation-model.xml structures like
taskflow://WEB-INF/test/testTF.xml#testTF in URL field, without adding the adf.jar to the project.
My ideia is to deploy the lib, but do not add it to the project, in order to allow decoupled development.
Thanks,
Joao,

Guest WLAN Deployment, and the EtherIP Process from Campus to DMZ WLCs

Hi All,
In the WLC deployment guide
http://www.cisco.com/en/US/docs/wireless/technology/controller/deployment/guide/dep.html
It has a very nice and easy way to understand how traffic is passed from the wifi device to the LAN device as listed below.
Now, what happens when there is a controller in the DMZ and the WLC on the campus passes this traffic to that controller via ethernet over IP.
Is the 802.11 header preseved or is it stripped off at the campus WLC? One would assume it is preserved as the WLC in the DMZ may need to act on information in the 802.11 header?
Can anyone help me on this please?
Is there a similar example to the one listed below, but for the full flow from end-user wifi device to the guest controller in the DMZ?
Many thx
Ken
In Figure 3, Host A is a wireless LAN client communicating with the wired device, Host B. When Host A sends a data packet to Host B, the following sequence occurs:
â¢ The packet is transmitted by Host A over the 802.11 RF interface. This packet is encapsulated in an 802.11 frame with Host A's MAC address as the source address and the access point's radio interface MAC address as the destination address.
â¢ At the access point, the access point adds an LWAPP Header to the frame with the C-Bit set to zero and then encapsulates the LWAPP Header and 802.11 frame into a UDP packet that is transmitted over IP. The source IP address is the access point's IP address and the destination IP address is the WLC's AP Manager Address. The source UDP port is the ephemeral port based on a hash of the access point MAC address. The destination UDP port is 12222.
â¢ The IP packet is encapsulated in Ethernet as it leaves the access point and transported by the switching and routed network to the WLC.
â¢ At the WLC, the Ethernet, IP, UDP, and LWAPP headers are removed from the original 802.11 frame.
â¢ After processing the 802.11 MAC header, the WLC extracts the payload (the IP packet from Host A), encapsulates it into an Ethernet frame, and then forwards the frame onto the appropriate wired network, typically adding an 802.1Q VLAN tag.
â¢ The packet is then transmitted by the wired switching and routing infrastructure to Host B.
When Host B sends an IP packet to Host A, the process is essentially reversed:
â¢ The packet is delivered by the wired switching and routing network to the WLC, where an Ethernet frame arrives with Host A's MAC address as the destination MAC address.
â¢ The Ethernet header is removed by the WLC and the payload (the IP packet destined for Host A) extracted.
â¢ The original IP packet from Host A is encapsulated with an LWAPP Header, with the C-bit set to zero, and then transported in a UDP packet to the access point over the IP network. The packet uses the WLC AP Manager IP address as the source IP address and the access point IP address as the destination address. The source UDP port is 12222 and the destination UDP port is the ephemeral port derived from the access point MAC address hash.
â¢ This packet is carried over the switching and routing network to the access point.
â¢ The access point removes the Ethernet, IP, UDP and LWAPP headers, and extracts the payload, which is then encapsulated in an 802.11 frame and delivered to Host A over the RF network.

Hi There, no worries. Would be good if there was a doco on it.
From packet captures (see attached) it looks like when the campus WLC gets the original 802.11 packet (which is encap'd in LWAPP), the campus WLC strips off the LWAPP stuff and removes the 802.11 packet header, and just rebuilds original packet with an 802.3 packet header,
THEN
The WLC encaps the packet with a new ethernet/IP header and sends it off to the DMZ WLC.
I hope this is the way it works, and if anyone does have documentation to confirm it, that would be fantastic.
Many thx and kind regards,
Ken

WLAN deployment across 3 floors without cable

I have a customer looking to install a wireless network across 3 floors with full coverage on each floor. 2 ssid's are needed one for guest use and one for their business use. The top floor is where the server and demarc is located. The top floor is very small in relative size to the lower 2 floors.
It is a very old historic building and they refuse to run cable (drilling of holes...)
They will need bandwidth to support 12 pos systems (varied throughout the building) running off of the server (terminal services). They will also need enough bandwidth for the guest ssid (internet use).
Installing a lot of ap's as repeaters will reduce the available bandwidth. What options are available?

Keep in mind, you'll need a solid site survey to back up any recommendations made.
That being said, probably your best would be a dual radio AP, where the 802.11g/b radio is for client use, and the 802.11a radio would act as a wireless backbone.
If you use a 1200 series, you'd want one AP (per floor) located in / near the stairway and/or elevator such that you can use it as a "raceway" for the 802.11a signal.
Depending on the size and layout of the floor (wide open, partitioned, trees/flowers/hanging decorations), you can perhaps cover the area with ~2-3 APs (each set for a different 802.11g channel: 1, 6, or 11 preferred).
You should stagger the AP channel assignments per floor such that the AP directly above or below is using a different channel.
This is greatly simplified. More details would be helpful (like the square footage of the each floor, and the general layout, are there going to be any mobile clients, or all fixed location POS stations?).
and, again, you must do a good site survey to find out how many APS would be needed. If you need more than three per floor, then it would probably be better to use the 802.11a radio for clients and the 802.11g radios for the "backbone" .... 802.11a has more channels, and none of them overlap.
Good Luck
Scott

Wireless Outdoor Networking

Hi Guys,
I have been doing a fair bit of work with indoor wireless networking. I was wondering if I could ask a couple of questions about outdoor wireless networks if I may :).
1. Wireless Mesh Networking. Is this really a solution to interconnect buildings over wireless with point-to-point connectivity?
2. How does a service provider like "the cloud" provide access over an area with wireless connectivity for end users? What kind of wireless network design would be employed here? Would they just have lots of APs in shopping malls that you would have like an indoor network, and how do they get the service coverage in open spaces, like roads, parks etc etc.
I am looking for info on both types of outdoor networks. Point to point only to connect buildings and flooding SSIDs within a large outdoor area in which customers can connect?
Can anyone help me, as this is a very interesting subject.
Also, have I got the term correct. A wireless Mesh network is for point to point wireless networks?
Many thx indeed,
Ken

Hi Ken,
Wireless Mesh is a different concept altogether, and it's really not intended to be used as a point-to-point bridge. Mesh is a way to deploy access points in an outdoor space or anywhere that's difficult to run a LAN cable to. This AP will use the 2.4GHz band for client connectivity, and it will send all backhaul traffic across the 5GHz link to another AP. As long as the 5GHz backhaul eventually finds a Mesh AP that is connected to the Ethernet network, it will have connectivity.
One of the best uses for Mesh is for large parking lots. You can mount an AP on a light pole, but you'd never want to run an Ethernet cable all the way out there. Instead, you'd use a Mesh AP and have the 5GHz radio pointed back at your office building, where another Mesh AP is plugged into the local network. So now your clients/customers can connect wirelessly to the AP in the parking lot, and the parking lot AP sends this data wirelessly to your building.
It's called Mesh because you can have a literal mesh of APs scattered across large regions, some of which are connected to the network, others of which are isolated with wireless backhauls. Cisco runs a proprietary algorithm for calculating the best path for traffic to flow to get to an AP with a network connection.
As for your question about a "cloud" company, it all depends on the design. You can install indoor APs that connect to antennas outside, and these can connect your clients. Mesh can be a better solution, but sometimes it's not needed when only small areas need to be covered. Plus, Mesh is far more expensive than a traditional design, especially since it requires wireless LAN controllers. But as for large areas like you're talking, such as roads and parks, Mesh is certainly the best way to go.
I hope that's more of what you're looking for. Let me know if you have any more questions!
Jeff

Voice over Wireless Outdoors?

Has anyone deployed outdoor VoWiFi?
I am charged with studying the feasability of an outdoor wireless voice solution for a large outdoor courtyard between several buildings.
The layout of the campus would require a mesh network. I would most likely use the new 1532I outdoor access points.
I am of the assumption that the phones would opperate on 2.4 Ghz and the APs would backhaul the data on 5Ghz?
In all likelihood, I could probably get it to work, but how well?
Would a deployment scenario such as this even be advisable to attempt?

Hey Philip,
VoWLAN for MESH is not recomeneded by Cisco for the following reasons:
- Mesh is less stable than the other AP modes like local
- Mesh will force the clients to use 2.4 GHz (unless for some very rare situations)
- Voice is not recommended for 2.4 GHz and all Cisco guides asks to use 5 GHz
- This scenario is not supported by the Cisco TAC
Cheers,
Nour

Application Deployment from Remote Share

I have a particularly large application I need to deploy and the source changes reasonably frequently so I don't want to add it to normal distribution points within SCCM. By that, I mean I don't want the entire 6GB to be copied up to the SCCM server, I want
it to stay put where it is, and the installer run from the share that it is currently on. Is there any way to achieve that?
And also, is there a way to stop the application downloading to the clients, again just installing from the share. So the app source doesn't get copied to the server or client at all?

Thanks, that sounds like a good compromise! By the way, how long does the client cache installs? i.e. if I went for the full deployment model so all 6gb got put in the DP and then cached to clients, will that 6gb cache stay forever? or can you tell it not
to cache at all?
Also, for a conventional deployment, what happens if the source files (on a different network share originally) get deleted or removed, does the DP continue to deploy the software and only have problems if it needs to update / refresh?

Guest WLAN accounts

I am working on Guest WLAN deployment using a anchor WLC and NAC Guest Access server for authentication. I now have a requirement to prevent Guest machines from logging in with the same set of credentials. I already have concurrent connections set to 1, but can I easily tie the user credentials to a Guest Machine when they login the 1st time.

I won't claim to be the expert, but I'm pretty sure that Guest login is a different "security" from your WLAN security. Whatever settings you use on your WLAN (WPA/WEP/etc.) must be configured in advance on the client in order for the user to connect to your wireless network and get an IP address. Once connected, the user will open up a browser (which will get redirected) to the guest logon page. At this point, the client can only resolve DNS and get to your guest logon web page. Once logged on, the user will be able to actually get somewhere on your wireless network, but the WLAN settings remain the same before, during, and after guest logon.
Also - if you can implement WCS, WCS will allow you to print or email the credentials.

Modularizing large FX gui apps, esp. using fxml developed by Scene Builder

StarterApp - One large java source file.
Trying Out the JavaFX UI Controls (Using the JavaFX UI Controls)
StageCoach is a simpler app, but with fxml, controller, and main code in separate files.
Allows manipulation using Scene Builder.
https://code.google.com/p/jfxtras/source/browse/ProJavaFX/Chapter03/StageCoach?repo=samples&r=322042d9ac293fcd9dd8f63e1664df45a0c4746f
I was lead to these by the book, Pro JavaFX 8:
http://www.apress.com/9781430265740
Rich as it is, the StartApp is one big piece of code, with no modules such as an fxml file.
By spreading out the code for StarterApp and StageCoach and studying it carefully
I should be able to build a system as large as StarterApp, but as a three-file combo.
StarterApp has nothing that deals with concurrency or persistence - those will be my jobs.
I'm doing this because I'm building a large NLP app.
It needs a GUI for future users.
- Bob F

Take a look at some app examples from the open-jfx repository
https://wiki.openjdk.java.net/display/OpenJFX/Quick+Start
For a smallish app, see the ConferenceScheduleApp:
   openjfx/8u-dev/rt: 3d138300d935 /apps/experiments/ConferenceScheduleApp/
For a (much) larger app, see SceneBuilder:
   http://hg.openjdk.java.net/openjfx/8u-dev/rt/file/3d138300d935/apps/scenebuilder
   Ladstatt: Home made JavaFX SceneBuilder
For a minimal framework which features FXML and dependency injection, see afterburner.fx:
   http://afterburner.adam-bien.com
You can skip all of the stuff below if you don't like reading and just want to go code...
In general for app code, use aggregation over inheritance in most places, though inheritance is useful sometimes. Don't try to create your own controls by extending the Control class unless you are writing control libraries - that is complex and not well documented as well as largely unnecessary for app code. Similarly PopupWindow isn't all that great or at least I have never found a need for it in app code - a basic Stage works fine for pretty much every case except perhaps very specialized things like context menus. Java 8 has built-in dialogs and alerts in 8u40, so for standard dialogs or some reasonably customized dialogs, using those is better than creating your own. If the standard controls aren't enough, try ControlsFX, it is (mainly) great and high quality.
Let resizable layout managers do the layout work for you and use constraints in the layout managers and nodes rather than mucking around with fixed sized layouts or layout through binding.
Don't try to implement a spreadsheet in a JavaFX TableView - just use the built-in controls for what they are good at and either develop a new control for specific functionality not provided by the built-in controls or just skip that feature if it would be too expensive to build it from scratch yourself (and it probably will be expensive - you just have to justify that against your project budget whether that is money or your own time).
Make use of WebView to bring in web components (e.g. Google Docs or Google Maps). Don't try and pass a lot of data back and forth between a WebView and your app.
Don't do any style in code nor in FXML, put it all in a CSS style sheet.
For medium sized apps - use FXML to design and mark-up your GUI, and use SceneBuilder to create and edit the FXML, don't hand code basic form style UIs - in the long run the FXML based app will be easier to maintain.
For really small apps and learning tasks, write everything in code against the API so you understand that - use no FXML at all.
With JavaFX you are writing user interfaces, follow basic user interface design heuristics for which there are some principles to keep in mind.
Once you have a few FXML pages, passing parameters or sharing data between them is a question that most people run into as well as how to deal with navigation. That navigation framework I linked is super basic and just meant for pretty simple applications. A nicer framework which worked in general like a Browser navigation model would be useful - but I haven't seen a generic implementation of such a thing yet - I guess you could create one, but I definitely wouldn't start out trying to do that - instead focus on the basics of your application and get that implemented first. If you end up needing a reasonably sophisticated navigation framework, eventually you will know it and can evaluate what to do then.
You can do an awful lot with CSS and styling the built-in controls. It really is very flexible. Learn CSS and the JavaFX variant by reading general CSS tutorials (then forget everything HTML specific) and study in depth the JavaFX CSS reference guide and understand its extensions like looked up colors and derivation functions. When you want to know how some inbuilt thing is styled, go to the modena.css source (which can be hideously obtuse and complicated). Use ScenicView and SceneBuilder CSS analyzer to understand how CSS is applied to elements. Don't style borders with boxes - use layered backgrounds, that is how every control modena.css works and how your app should also work.
Deployment is a difficult topic - so sad and depressing. For development, just build and run in your IDE. For production, package the app as a self-contained application. Maybe one day there will be a better deployment model for JavaFX - but that is the best you can get for now. Completely ignore webstart and web deployment models - any time spent investigating such technologies is completely wasted.
Do not try to integrate JavaFX and Swing or SWT. Just write pure JavaFX apps.
For larger apps you intend to deploy to production, use Maven or Gradle as your build system (you can google the JavaFX plugins for each). Do not spend any time with the stand-alone JavaFX packager or the JavaFX ant tasks and do not rely on your IDE to do your production builds.
Get help to targeted questions on StackOverflow.
Only code to Java 8+ and make use of functional programming techniques.
Don't write multi-threaded apps unless you know what you are doing. When you do write multi-threaded apps, use the JavaFX concurrency utilities. Never modify the active scene graph from another thread, nor touch a property which might trigger an event which might modify the scene graph. Do use the concurrency utilities if you have network I/O otherwise you will freeze your app while the network I/O occurs and that is a "bad thing".
The Oracle JavaFX 8 documentation is good - read it and run a lot of the examples (except the ant based deployment ones and the Swing/SWT integration ones).
Ensemble is great, play with it and study the code to see for the samples (which you can view within Ensemble).
Binding is programming by side-effect, so be aware that when you change a property, it may trigger some potentially unrelated action through bindings or attached listeners.
Programming JavaFX in any language other than Java is an experimental thing, so only do that if you like experimenting and are prepared to do so without a lot of support.
Targeting embedded devices, iOS or Android for a JavaFX app is an experimental thing, so only do that if, yada, yada, yada.
JavaFX is a mid-level UI system, not a full application stack - it abstracts away the basics like rendering, controls and animation but does not provide comprehensive OS hooks, navigation frameworks, model/view/presenter frameworks, full dependency injection, client/server messaging, data <-> controls serialization and deserialization, etc. FXML is just a markup system with a binding capability to Java code. JavaFX and FXML do not constitute a full application framework. There is no widely-used full application framework for JavaFX. Sure some people have tried to create one, but none of those solutions have achieved critical mass of usage and features - plus a one-size fits all application framework will never exist anyway - client applications (e.g. a game versus a line-of-business app) differ greatly and deserve completely different architectures.
There are many things in the Java EE world which can be used in JavaFX (e.g., its dependency injection, its web socket or rest APIs and implementations, its server based systems to allow your app to access cloud based logic and storage, etc) - so feel free to use the bits you need, usually it's as simple as adding additional library dependencies to your maven or gradle project. A typical medium sized JavaFX application will include multiple third party libraries (mostly non-UI libraries) to get its job done as this will be more convenient than coding everything against the JRE API - though there is an awful lot of out the box functionality you get from the JRE.
JavaFX is more complicated to use than Delphi and in some respects doesn't supply as much functionality in terms of built-in stuff like data base backed tables (though it supplies a ton more functionality in style). It is not easier to create a complete business app using JavaFX than it would be to create a similar thing in Microsoft Access in the 90's. Such is progress.
JavaFX is portable across desktop environments (OS X, Windows, Mac). JavaFX apps have their own look and feel which is not like the native OS, but that is probably fine for a lot of apps. AquaFX does an amazing job of making a JavaFX app looks like OS X apps (kudos to the creators of both AquaFX and the JavaFX built-in styling capabilities).
Unlike some other portable frameworks like QT, you don't have to write C code, you can write Java code (which to me at least is a win). Similarly unlike HTML/CSS/JavaScript you don't have to write untyped JavaScript or make use of some obscure code snippet you pulled off the web for your button control. You don't have to use the web framework of the day which withered yesterday. Instead you have the (benefit?) of hardly any framework at all for JavaFX. You don't have to have your app live within a browser sandbox that another developer once described as the ghetto of application sandboxes.
So, as compared to HTML - I think JavaFX is kinder to the developer, though end users don't really seem to care that much and are fairly accepting of HTML applications even when their functionality is often inferior to many more traditional GUI apps. HTML is standardized, its full of standards, even the non-standard parts. Everybody used to implement all the standards differently or make their own standards, however now the standards are so painstakingly, nitpickingly prescriptive that everybody implements pretty much the same thing - except when they don't. JavaFX has no standard but its public API docs, it has just one implementation. If you code against the API, your app is probably going to work forever - at least if you bundle the runtime with your app, cause if you don't you might end up like the poor guy in the previous question who can't figure out how to update his app specific CSS rules to get his app to look the same with a newer Java version. JavaFX is a relatively niche technology and you don't have the legion of developers, tinkerers, industry investments and people just plain getting stuff done in any which way that you have with the whole HTML juggernaut. The major thing that HTML provides that JavaFX does not is: Sharable, browsable deep links to stuff with search indexed content. With HTML, Google will index it and you can link to and refer to other docs and other docs can link to yours. It is the HT in HTML which makes the web so amazing and the F in FXML doesn't match it. What is the F anyway?
That's a huge wall'o'text. Just some random thoughts and opinions. All opinions are my own. Your opinions may vary. That's OK. I don't think a discussion is needed. If you would like any clarification or further advice you can ask in new questions.

Centralised multisite controller deployment

Hi All,
There is one centralised controller that exist at the head quarters and the access points are distributed between two locations. The remote site needs to get guest wireless access through the controller. All services reside at the main site however dhcp can be received at the router in the remote site. Please advise if this scenario is possible and also explain how.
Thanks

Hello Steve,
Sorry for the late response but the customer would like all guest traffic to remain local since the remote site has an internet connection.
Given this requirement you said that only a vlan is needed and this needs to be mapped to the HREAP settings?
Now since the guest network is a new network that will be created on the remote site, will the hub site need to know how to route to this network since the WLC lies there? The dhcp server is local at the remote site.
My confusion is role of the dynamic interface in the WLAN deployment.
When a client connects to the guest-wlan, which is configured with central auth (web-auth) and local switching, after the auth is successful, what happens next. Will the WLC need to know the gateway of the guest-wlan gateway?
My query is more on the routing needed from the hub site to spoke site for the guest wlan that is local to the remote site.

WLAN Client Roaming

I have a WLAN deployment with around 40 APs and dual WLC4400's. For some reason the clients seem too "sticky" to their first associated AP and don't roam. How can the system be tuned to make them roam to other AP's better?

Ok Rick,
I have seen similar problems before when utilizing client server applications such as Citrix or SAP. I do need to know if the APs are actually providing good coverage so I am assuming you had a good survey done here. There are several client sticky conditions that have been found to be caused by 11mb beacons and eap issues. Try these settings:
Security => Credentials cashing enabled (eap credentials)
Improves roaming performance
Wireless => Global RF 802.11b/g
changed 11Mbit from mandatory to supported
Apparently there is a known issue with 11Mbit beacons,
disabling them also assists in better roaming.
If you would like me to look over your physical network of APs and coverage, send me a copy of your current survey. One other thing, which APs are you using and what antenna configuration. Noise and multipath can also contribute to longer roam times but I am betting on the thin client being the problem here.

Deploy all O365 ProPlus software in image...

Hi,
We plan to jump to O365 Pro plus (Faculty license) in the near future. At the same time all staff will receive new computers. We would like to pre-install O2013, Lync 2013, SkyDrive Pro and whatever is required via MDT / WDS to each computer
so everything is as ready as possible when the user logs on the new computer for the first time.
Where do we find installer packages for all this software and what is actually required to have this play together without yelling about product keys etc..? Or - do we simply have to resign and let the users do it the hard way by downloading and installing
themselves?
Thanks for comments and links :-)
regards Tor

However, *where* do I find the installer files for the correct edition of O365ProPlus? I assume that I cannot use the Trial version available online. Or do I have to purchase an installer? I assume this is neither the OEM nor MAK
edition so I'm at a loss here.
O365ProPlus is a specific edition of Office, it's not available via OEM, and MAK/KMS does not apply since O365 is subscription-based only.
The ODT (Office Deployment Tool) is the downloadable tool, used for downloading the O365 (and other) source files.
O365ProPlus is packaged in Click-To-Run format (aka C2R) which is an extended form of App-V.
It uses a large binary blob/stream to deploy a virtualized installation package, it doesn't use traditional MSI/installer methods.
The links, and documentation, for ODT, are in the link I gave you above :)
The ODT, and stream/source ODT pulls down for you, is all available publically, there's no need to purchase that.
The licensing is all determined/controlled by the login/identity you input *after* installation, when you launch an Office application. That's the point where your entitlement/subscription is validated. Which is where your identity strategy either works,
or screams *FAIL*FAIL*FAIL* at you ;)
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

8 or 16 WLANs Supported

Ok, I've been searching everywhere and I can't seem to find the answer. I know the WLCs support up to 16 WLANs but I could have sworn that I saw that only 8 could be active at one time. We are running a combination of WISM, WLC 4400, and WLC 2100s in our environment. The only places wer're going to need more than 8 is at our WISM and WLC 4400 locations.
Any help is appreciated (and supporting documentation if you have it).
Thanks all!
Ryan

I dont have the docs in front of me, but I know that the 6.0 code supports more than 8 (I believe 16), since we currently have 10 WLANs deployed during our migration. -John
Edit: Found this in the 6.0 WLC config guide:
All controllers publish up to 16 WLANs to each connected access point, but
you can create up to 512 WLANs and then selectively publish these WLANs (using access point groups)
to different access points to better manage your wireless network.
And this from the 4.2 guide:
The Cisco UWN Solution can control up to 16 WLANs for lightweight access points. Each WLAN has
a separate WLAN ID (1 through 16), a separate WLAN SSID (WLAN name), and can be assigned unique
security policies.
Message was edited by: [email protected]

Large outdoor /i ndoor WLAN deployment

Similar Messages

Maybe you are looking for