Wacom Bamboo & Intuos5 Tablets Wireless Option - digitizer connection kit

Mfg. Part: ACK40401 | CDW Part: 2687554 | UNSPSC: 56112005
$41.99Advertised Price

Have leasing questions? Let us know how can we help.

Note: Leasing is available to businesses only. Leasing is not available to individuals.
Mon-Fri 7am-7:30pm CT
Availability:2-4 days
Orders placed today will ship within 4 days
  • Digitizer connection kit
View More
Product Overview
Main Features
  • Digitizer connection kit
More space for your life. With the Wacom wireless accessory kit, your tablet can easily connect wireless with your computer.
Technical Specifications
Specifications are provided by the manufacturer. Refer to the manufacturer for an explanation of the print speed and other ratings.
Brand: Wacom
Compatibility: PC
Manufacturer: Wacom Technology
Model: Wireless Accessory Kit
Packaged Quantity: 1
Product Line: Wacom

Compliant Standards: Plug and Play
Product Type: Digitizer connection kit

Category of Accessory: Pointing device accessories
Package Content: Rechargeable battery , Wireless receiver , Wireless transmitter

Product Reviews
Rated 3.4 out of 5 by 7reviewers.
Rated 3 out of 5 by PRO: flexibility when setting up our builds. CON: lacks support for branched builds using multiple source repositories Valuable Features:We are very fond of the flexibility it offers in terms of setting up our builds. We have a wide variety of components we need to build which often require custom actions or manipulations using in house technology. Bamboo allows us to set this up quite easily by the flexible configuration features it includes.Secondly we really like the integration of the build aspect and deploy aspect. One of the recent major releases included this feature to link build and deploy projects together allowing a deployment pipe-line to be setup completely in Bamboo. This makes the status of deployments very visible and also allows for easy follow up and even rollback in case a deployment causes too much havoc.Improvements to My Organization:Thanks to Bamboo we are able to build changes made by development quite quickly and allow them to deploy to our internal environments when needed (as well as automated during the night). This significantly reduces the effort required to get something into test.The fact that all builds use a unified setup and infrastructure makes it much easier to control and adapt the ever increasing number of builds.Room for Improvement:We are lacking proper support for branched builds using multiple source repositories. The current approach is quite clunky (or non-existent) but it seems there is something in the pipe line for the end of the year according to a recent post on the Bamboo Jira.Use of Solution:We have been using Bamboo for about 6 years nowDeployment Issues:Not at all, over all those years we only had a handful of issues and that's probably because we always take each new update directly.Stability Issues:No, we never encountered any serious regression. For the few cases we encountered bugs they were fixed in a reasonable time interval.Scalability Issues:Scaling out a build system is not always easy, but thanks to the remote agent technology we are able to scale out and add nodes in a transparent way.Customer Service:We use a 3d party for our license management, which makes it hard to judge this but we never had direct interactions with Atlassian Customer support.Technical Support:Pretty good once you get trough the initial levels of the support team, it can take a while before you are able to prove that there's a genuine issue.Previous Solutions:We came from Jenkins back in the day, I recall our most important reasons to switch where the enterprise readiness of Bamboo and its integration in the Atlassian stack (Jira and others).Initial Setup:Bamboo is very easy to deploy, all it takes is extracting the distribution and a JRE to run it. This also goes for the remote agents which install by running a JAR which already contains the configuration for communicating with its master.Implementation Team:We implemented in house.ROI:That would be 100%, the time saved in development is enormous.Cost and Licensing Advice:We started out using only a number of agents and moved to a bigger setup using many remote agents over the years. The cost depends on the agents used and amount of boxes deployed to run them on.Other Solutions Considered:Only Jenkins, see previous answer.Other Advice:Plan before you start, Bamboo is 'only' that which automates. One should have a decent design of how the build needs to work internally and have that (scripts, servers, descriptors ...) in order before attempting to automate on a large scale.Secondly, don't be afraid to change things to you application or pipeline to help the automation to be more efficient - for example we replaced massive chunks of hard SQL from the build scripts by a webservice to avoid dependencies to JDBC in our builds.Disclaimer: I am a real user, and this review is based on my own experience and opinions. June 10, 2016
Rated 4 out of 5 by The REST API for our deployment project is still very basic, but with Bamboo, we've been able to implement an on-demand, push-button release strategy. Valuable Features:The Deployment ProjectImprovements to My Organization:Bamboo, along with its integrated deployment and release pipeline, enabled us to go from a monolithic, once a month release cycle, with many post-release incidents to an on-demand, push-button release strategy where we deployed over 200 times a month with very few to no release-related incidents.Using this tool, we were able to empower the dev teams to push their own changes to production rather than rely on the operations or release teams to release it.Room for Improvement:The REST API for our deployment project is still very basic and lacks the ability to provide a decent amount of custom automation. For many things, we had to resort to direct database queries simply because certain data was not exposed via the API.Use of Solution:I've used it for five years.Deployment Issues:No issues encountered.Stability Issues:Every once in a while deployments would hang and we weren't able to clear them without restarting the service. It didn't happen a lot and it may have been due to how we configured the app on the server.Scalability Issues:Not really. As long as your organization is willing to pay a bit more, Bamboo can scale to meet your needs.Customer Service:7/10 - sometimes you just want to talk to someone over the phone, but this isn't very easy with Atlassian. They have a ticket support system that's pretty good at connecting you with a customer service rep, but sometimes this means you have to go back and forth, waiting for the representative to reply on the issue in order to isolate a problem.Technical Support:7/10 - sometimes you just want to talk to someone over the phone, bu this isn't very easy with Atlassian. They have a ticket support system that's pretty good at connecting you with a customer service rep, but sometimes this means you have to go back and forth, waiting for the representative to reply on the issue in order to isolate a problem.Previous Solutions:Bamboo was already being used.Initial Setup:It was pretty straightforward. Atlassian standardizes setup across products for the most part, so it was easy for us to install, configure, and navigate.Implementation Team:We implemented it ourselves in-house.ROI:We got a ton of product and development time back across the board, which could be translated to several tens of thousands of dollars.Cost and Licensing Advice:Keep in mind that Bamboo pricing is based on number of remote agents. Agents are what you used to load balance build and deployment tasks, so depending on how large your development shop is, what your software architecture looks like, and how often you intend to build and deploy new versions of software, it can get fairly pricey to support a higher volume pipeline.Other Solutions Considered:We evaluated Jenkins and Thoughtworks Go. At the end of the day, Bamboo just integrated better with the other tools we were already using - JIRA, Stash, Confluence - and provided better push button deployment control. Bamboo provided such a seamless delivery pipeline and visibility to all stakeholders through its easy integrations with our already existing toolset.Other Advice:Make sure you don't become dependent on the tool for basic delivery of software. And this goes for any tool you use for automating the building and deploying of your apps. Meaning, if Bamboo were to go down for whatever reason, you want to make sure you can still build and deploy software. To avoid Bamboo becoming a single point of failure, have all of your script tasks run a file that is managed in a repository instead of writing it in line in Bamboo.Disclaimer: I am a real user, and this review is based on my own experience and opinions. August 20, 2015
Rated 4 out of 5 by There are some stability issues with Java 6, but it offers build agents for Windows and Linux. Valuable Features:* Multiple build agents for both Windows and Linux* Automatic branch building - same build plan for trunk and branches* Connections with other Atlassian tools - JIRA and FishEye/CrucibleImprovements to My Organization:We have many developer teams building in Java, especially our Continuous Integration team. Bamboo has proven its value for the teams.Room for Improvement:There are no areas that need improvement.Use of Solution:I've used it for seven years,Deployment Issues:No issues encountered.Stability Issues:Once, with Java 6, there were some issues, but thanks to information from Atlassian support we changed to Java 7 and it works fine.Scalability Issues:No issues encountered.Customer Service:I'm satisfied, 8/10.Technical Support:I'm satisfied, 8/10.Previous Solutions:We used CruiseControl, and we switched because of better functionality in Bamboo.Initial Setup:It was straightforward, as the default agent and remote agents install out-of-the-box. Only some memory tuning was needed.Implementation Team:We did it in-house.ROI:It's hard to say, the yearly license/support/maintenance costs are low in relation to the added functionality.Cost and Licensing Advice:I see no problem in paying for support, especially because licensing is remote agent based.Other Solutions Considered:* CruiseControl* HudsonOther Advice:It's dependent on how many build teams you have. For small development sites, Hudson or Jenkins will suffice, I think. Because we’re building our main applications in-house, we always choose supported and licensed tools.Disclaimer: I am a real user, and this review is based on my own experience and opinions. July 29, 2015
Rated 3 out of 5 by Bamboo easily integrates into an Atlassian stack. Valuable Features:Ability to interface easily with other Atlassian applications.Improvements to My Organization:It allows a controlled process in which to build software.Room for Improvement:Version control for plans is currently not really possible. This is pretty much the deal breaker for me and why I'm moving away from Bamboo.The Upgrade process is also clumsy and requires manual steps. I'm not a fan of tarballs.Use of Solution:3 years.Deployment Issues:You may need to upgrade in steps if you are upgrading a relatively old version.Stability Issues:At one time we used to have issues with system stability. You may need to tinker with your systems heap settings.Scalability Issues:You are limited by the number of agents you are willing to buy. This means all your teams end up building on the same agents or worse, the master itself.This is the second deal breaker for me and why I'm currently advocating to move to a different build system.Technical Support:Atlassian support is usually pretty good in my experience.Initial Setup:They need to work on their upgrade paths and deployments. If you fall to a few versions behind you may end up doing a multi-version installation. Not fun.Cost and Licensing Advice:The license is the worst. It costs the most. In addition to that we run it on a very beefy server (HP DL360 G8 with 24G of ram). I would not run this software on subpar hardware.Other Advice:Pros:- Integrates well with Atlassian products- Nice Modern InterfaceCons:- Agents are limited by the license- No method to provide version control for Build Plans- It's expensive- Most plugins cost $$$Personally I'm in the process of moving away from Bamboo. Sure it looks nice, but I need flexibility. If you plan on creating a build server for each of your teams or projects, don't use Bamboo and use Jenkins instead. It has a richer plugin base, no limit on agents, and allows version control of plans and configuration easily. It's also open source software so the cost is much lower. Maintaining Bamboo is also a chore, not so with Jenkins which is distributed as a RPM, DEB, and now Docker container. Bamboo I'm still stuck downloading a tarball.Disclaimer: I am a real user, and this review is based on my own experience and opinions. February 24, 2015
Rated 2 out of 5 by The new Salesforce plugin looked interesting despite the fact you had limited control on how the SF package is deployed. Valuable Features:The deployment mechanism was neat, and I liked how it allowed you deploy the same release to multiple environments. I also thought the ability to branch build and deployment jobs without needing to use templates or updating job configuration could be useful. Plus the new Salesforce plugin looked interesting despite the fact you had limited control on how the SF package is deployed.Room for Improvement:* Logging, no integration with Octopus* Build time variables did not have ability to select from a list of value* No ability to customize Build version* TFS plugin had no local workspace editing of checked out files, as all files coming from TFS have read-only attribute turned on by design* No history view column adjustment* Password variable values were not concealed within GruntJS logs* Watching build log GUI loses focus at build completion making debugging difficult* Mediocre .Net Code Coverage support and reporting.Use of Solution:These observations were part of a multi-department, one month evaluation where we decided to go with a different product in the end.Deployment Issues:No issues encountered.Stability Issues:No issues encountered.Previous Solutions:We were using TFS for build automation. TFS proved to administrative to maintain and customize build templates. Plus we were planning to move to Git and found Git's interface within TFS/Visual Studio lacking in comparison to other Git clients.Initial Setup:It was straightforward, although, Bamboo initially creates its main install folder in the home directory of the current user. Even though Bamboo has a 'bamboo.home', Bamboo organizes its different library/build-time/resource component folders separately in the configuration and modifying those proved intensive in comparison to TeamCity and Jenkins where there's is only one 'Home' folder.Implementation Team:In-house.Other Solutions Considered:We evaluated TeamCity and Octopus.Other Advice:While the community may grow over time, please ensure your current/future processes are not hindered by Bamboo's faults. Bamboo is likely to improve with time, it may be advisable to use a different solution until the product grows a bit more mature.Disclaimer: I am a real user, and this review is based on my own experience and opinions. February 16, 2015
Rated 3 out of 5 by APIs were helpful for creating customizations but there are limited options with SSH plugins Valuable Features:* Integration with Atlassian products like Jira,Crowd, and Stash* Easy to setup* PriceImprovements to My Organization:* With Bamboo's integration with Jira, we were able to update build status and test reports to Jira bugs/tasks.* In Stash, we were able to improve the pull request review standards by being able to review the build and test reports.* Integration with Artifactory, helped us in auto updated libs and artifacts.* APIs were helpful for creating customizations.Room for Improvement:* Ease of use.* It needs "re-build/Trigger build" switch from Stash Pullrequest.* More 3rd party plugins to support IDEs.* Integration of older plugins with newer version of Bamboo.* More options for deployment plans* Configuring tools to agents (Had to do it manually). It would be nice have sharing from server.* -Docker support* Limited options with SSH plugins, can't use options to itUse of Solution:Two to three years.Deployment Issues:No issues with deployment.Stability Issues:Yes, Regular server/agent being down.Scalability Issues:Yes, It needs to allow multiple plans to run on a agent(at same time). Dedicating one whole agent isn't fair, I know we have to buy more agents, but in-terms buying and maintaining more infrastructure isn't scalable either. .Customer Service:Never used it. Had a decent responses from open forum.Technical Support:Never used it.Previous Solutions:Yes. since we wanted to keep Atlassian suite all-around.Initial Setup:Easy. Just like other Atlassian products.ROI:We got the product for a cheap price, so its alright.Cost and Licensing Advice:We initially got 5 agents for around $2000 excluding infrastructure setup. Now we are using docker containers to maximize the mileage on them.Other Advice:If you are looking for good integration with Atlassian products and then this is the tool.Disclaimer: I am a real user, and this review is based on my own experience and opinions. January 14, 2015
Rated 5 out of 5 by Works Great The wireless option with the Wacom Intuos tablet works like a charm. Downloaded a whiteboard program and we have turned our 60" conference TV into a whiteboard! August 21, 2014
  • 2016-10-30 T09:35:38.862-05:00
  • bvseo_lps, prod_bvrr, vn_prr_5.6
  • cp-1, bvpage1
  • co_hasreviews, tv_7, tr_7
  • loc_en_US, sid_2687554, prod, sort_default
1-7 of 7
Adding to Cart...
12/3/2016 4:16:21 PM
^ Back to Top

Maximum 300 characters
An account manager will email you within one business day to confirm your request.

Your Quote has been submitted

What Happens Next? A confirmation email is on its way. Within one business day, you will be contacted by an Account Manager to finalize your quote.


Something went wrong.

Please try again later.

License Selector

    The license selector is not currently available. Please try again later.