DMS Systems, Data, Security, I.T.

A Ford dealer seeks recommendations for software to manage content uploads to their dealership billboard after their previous vendor closed. Community members suggest Screenscape (a general-purpose digital signage platform), AdArt (specifically for LED street signs), and Screenly (a Raspberry Pi-based freemium option noted for reliability). The thread highlights that solution selection depends on the specific billboard type, with multiple viable options available for different hardware configurations.

A dealer questions whether Dealercenter's claim that switching website vendors would break their Westlake Financial credit app integration due to SSL certificate issues is legitimate. Community members confirm the technical limitation is real but offer a workaround: iframing the Westlake form into any new website vendor should preserve full functionality, including direct data import into Dealercenter, since the form submits to the same Westlake servers regardless of where it's hosted.

A Dealertrack user asks whether their DMS supports "power posting," a feature their office manager mentioned exists in ADP and REYREY systems. A fellow user responds by requesting clarification on what power posting actually does and where it's located, indicating the feature may not be widely known or standardized across DMS platforms. The thread does not appear to reach a resolution or conclusion about power posting's availability in Dealertrack.

A Ford dealer (Claire Kultgen) shares their experience switching from Reynolds to DealerTrack after 25+ years, reporting a smooth transition aided by thorough data verification, while another dealer (Eley Duke) warns that switching from ACS to DealerTrack proved rougher due to data transfer issues with parts and service data. The key insight is that DMS migration success depends heavily on the source system—transfers from ACS were problematic, while transfers from Reynolds or ADP tend to be cleaner—and that meticulous pre-switch validation can prevent major issues.

A BMW dealership needs to reconfigure a Cisco 3560 switch that Reynolds and Reynolds previously managed but is now locked with unknown credentials; Reynolds refuses to support it since the dealership no longer uses their DMS. After exploring options, the user decides to perform a password recovery procedure on the switch, though some forum members suggest just replacing the aged equipment instead—however, the original poster reveals BMW requires them to keep this specific switch model.

Dealertrack DMS users share their early experiences transitioning from the legacy IBM iSeries console to the new web-based DMS 2.0 platform. While users praise the browser compatibility and new Business Office features, they report workflow challenges including reduced keyboard shortcuts and tabbing functionality, with some departments (like Parts) preferring the faster legacy system and others encountering freezing issues during heavy general ledger posting. Dealertrack's dedicated support team is actively addressing these performance issues, and overall sentiment is cautiously positive as the platform matures.

Automotive professionals discuss potential applications of Google Glass in dealerships, with limited real-world adoption reported. While some saw promise in service departments using the technology for remote assistance and data collection, and manufacturers like Hyundai and Chevrolet were developing companion apps, the high cost and growing consumer privacy concerns ultimately discouraged practical use in the industry.

A dealer seeking software to prevent overbooking delivery appointments in their F&I office receives recommendations for appointment-scheduling tools, with Appointment-Plus emerging as the preferred solution due to its allotment function that prevents double-booking. The original poster identifies delivery scheduling as a key pain point affecting CSI scores and customer experience, and plans to implement Appointment-Plus to help sales staff provide realistic delivery windows rather than overpromising to customers. While responses reveal dealers use various methods (from spreadsheets to specialized software like Shopwatch and Schedulicity), the consensus centers on Appointment-Plus as the most effective tool for managing capacity constraints in the delivery process.

A dealership employee transitioning from ADP to Dealertracks asks whether there's a more efficient method to adjust part quantities on orders after the initial entry, rather than having to navigate back to the part line and re-enter the quantity. A respondent confirms that modifying quantity after a part is already added to an order requires using the same process (the "Q6" method), though quantities can be specified upfront when first entering the part number.

A dealer inquired about automotive diagnostic devices similar to Allstate's Drivewise product for potential business use. A community member recommended Torque Pro, an Android app that provides diagnostic information and reads fault codes comparable to insurance telematics apps. The original poster found this recommendation satisfactory and marked the inquiry resolved.

Daniel Mondello seeks peer feedback on Contact at Once's texting product for dealerships, questioning whether it actually drives sales results. Cmjerry4531 shares experience that a texting option generated 40-70 additional monthly leads without cannibalizing other channels, though most inquiries were simple inventory questions and conversions were unclear. The thread suggests texting functions primarily as a low-friction communication touchpoint rather than a proven revenue driver, with value depending largely on individual dealership metrics and compensation structures.

Mercedes-Benz dealership IT professionals and managers collaborate to troubleshoot chronic issues with the NetStar web portal, including browser incompatibilities, outdated Java requirements, and conflicting technical support guidance. Contributors share practical workarounds such as adding NetStar domains to IE's Trusted Zone, using compatibility mode for certain modules, and adhering to specific legacy software versions (IE 8-9, Java 6u32), while expressing frustration that Mercedes-Benz corporate IT ignores modern security standards and real-world operational efficiency needs. The core insight is that NetStar's reliance on dated technology creates a security liability, yet MB tech support prioritizes stability over security rather than modernizing the platform.

A dealer seeks technical guidance on authorizing ERA's Dynamic Reporting Option and identifying the executable needed to build reports. One user suggests executable 6910 as the answer, while another response jokes about replacing Reynolds (the DMS vendor) with a more modern alternative, drawing agreement from a third user.

A dealer seeking to replace their current DMS due to poor usability, lack of web-based functionality, and disconnected systems asks the community for real-world feedback on DominionDMX after seeing an impressive demo. The only substantive response advises conducting full in-store demos of multiple DMS systems before making a decision, noting that most modern systems integrate accounting. The thread appears incomplete and lacks detailed user experiences with Dominion specifically.

A prospective IT director for a new Ohio dealership inquires about Automate DMS's in-house server requirements, inventory-to-website integration capabilities, and server architecture, expressing frustration with slow initial response from the vendor's sales team. A company representative (Jlewis74) provides key answers: Dell servers are used and pre-loaded before shipment, inventory can be synced to websites, and the system runs on Linux. The thread concludes with the vendor acknowledging the communication gap and committing to direct outreach to the prospect.

Nissan North America notified Reynolds & Reynolds DMS users that a recent system upgrade has cut off NNA's access to critical dealership data (parts, service, sales, inventory), disrupting several NNA programs and performance metrics. The thread touches on Reynolds & Reynolds' broader reputation for aggressive contract tactics and vendor lock-in practices, with one dealer example from 2014 illustrating the company's ultimatum approach to force long-term contract signings. The key insight is that these data access issues represent another pain point in the contentious relationship between Reynolds & Reynolds and dealers who feel trapped by expensive systems and unfavorable contract terms.

A new employee unable to access deal and customer information in Arkona DMS receives guidance that their limited menu options indicate a permissions issue requiring their security officer to grant Business Office access. The respondent also directs them to use the built-in Help feature accessible from the top right of the DMS interface. The key insight is that functionality restrictions in Arkona are typically permission-based rather than user error.

A dealer inquires about Axcessa, a data reporting tool that pulls reports from Reynolds DMS systems, expressing skepticism about its capabilities. A respondent who recently implemented Axcessa with DealerTrack DMS reports positive results, highlighting significant time savings by eliminating manual Excel work and enabling faster decision-making based on key metrics. The thread raises questions about why Reynolds would allow a third-party tool to access their system rather than developing robust reporting themselves.

A dealer seeks legal precedent establishing ownership rights over dealership data stored in DMS systems. While responses suggest consulting state dealer associations for legal guidance, the conversation shifts to practical frustrations with Reynolds & Reynolds specifically, with multiple users sharing experiences of difficulty retrieving their data after leaving the vendor and concluding that legal action is unlikely to succeed due to the company's resources and stonewalling tactics.

A dealer asks for recommendations on effective service department loyalty and rewards programs. One respondent cites Fletcher Jones Motorcars' savings card program as a successful example, suggesting that tiered or card-based reward systems may be worth investigating for dealers looking to improve service customer retention.

Automotive dealers discuss cost-effective email hosting options, with Rackspace, Office 365, and Google Apps emerging as the main contenders, all priced around $2-6 per user monthly. The thread reveals a debate between feature-richness (Exchange/Office 365) versus simplicity and value (Google Apps, basic Rackspace hosting), with a secondary discussion about privacy concerns that ultimately highlights most dealers' needs don't justify premium security requirements. The consensus is that the choice depends more on existing business tools, team preferences (LibreOffice vs. Microsoft Office), and organizational requirements rather than cost alone, with negotiation recommended across all providers.

The thread discusses the impending end of Windows XP support in April 2014 and its compliance implications for dealerships, with Kevin McMillen advocating for cloud-based SaaS solutions as an alternative. After community moderators call out the sales-heavy tone of the initial posts, the discussion shifts to practical concerns: dealers' tendency to purchase cheap consumer-grade PCs unsuitable for business use, and the need for proper investment in compliant technology infrastructure. The core insight is that dealerships have historically underinvested in IT infrastructure and licensing, creating security and compliance risks that require a deliberate transition to supported platforms.