Stepping into the cloud should feel like progress for healthcare organizations—but it also comes with a new set of challenges that can’t be ignored. In a recent Forbes article, Forbes council member and Aviatrix’s chief product officer Chris McHenry breaks down why the industry needs a major shift in how it thinks about cloud security and compliance. The old “build a wall around the data center” mindset is outdated, especially when 276 million health records were breached in 2024 alone.

Healthcare systems are moving massive platforms like Epic’s EHR into the public cloud to boost performance, support telehealth and expand AI capabilities. All of that is promising, but fewer than half of IT leaders feel confident managing these new environments—meaning misconfigurations and blind spots are almost guaranteed. Regulators are tightening the rules too, with expected HIPAA updates calling for mandatory MFA, strong encryption, ongoing penetration testing and tighter network segmentation.

The core issue? Cloud environments don’t behave like on-prem networks. Workloads shift constantly, APIs connect to external partners and staff access apps from anywhere, creating a much wider attack surface. Recent incidents—like the Change Healthcare ransomware attack and Shields Healthcare Group breach—show how fast things can spiral without proper visibility and segmentation. McHenry’s take is straightforward: the future belongs to organizations that rethink security from the ground up. That means adopting zero trust, segmenting workloads, encrypting everything, automating compliance and gaining real-time insight into where PHI travels. He concludes that the cloud can absolutely transform care and innovation—but only if security evolves right along with it.

 

For Full Article, Click Here

 

In a recent TechRadar article, product marketing professional Steve Leeper argues that legacy data migration is no longer effective in today’s complex IT environments. What used to be a simple “move the files” task has become far more challenging as organizations now juggle hybrid infrastructure and massive volumes of unstructured data—over 80% of what enterprises store.

According to Leeper, the core issue is that traditional migration tools treat all data equally. They can’t interpret context, value, or risk, which often leads to companies transferring stale, irrelevant, or sensitive data into the wrong storage environments. Instead of improving operations, legacy migration can create new inefficiencies and expose organizations to unnecessary risk.

Leeper says the fix starts with rethinking the entire process. Migration shouldn’t begin with moving data—it should begin with understanding it. Organizations need clarity on what they have, who owns it, how it’s used, and whether it still matters. Modern intelligent data management platforms make this possible through metadata analysis, automated classification, and policy-driven workflows.

With automation and analytics in place, migration becomes a strategic tool. Teams can align storage investments with data value, prioritize hot data for high-performance environments, and archive or delete cold data with confidence. This approach also supports stronger governance, streamlined cloud adoption, and cleaner long-term data landscapes.

Leeper notes that successful organizations treat migration as part of broader modernization efforts, not a one-off project. They track KPIs—cost reduction, compliance, accuracy, and accessibility—to improve future migrations and avoid disruption.

Ultimately, he concludes, modern migration is about creating adaptable, well-governed data ecosystems that evolve with the business—not just moving data from point A to point B.

 

For Full Article, Click Here

Follow these simple steps to know how to resolve the Lawson Error, “Unable to remove object delete failed”

 

You may come across the following: Unable to remove object (RQRequester), delete failed. Original Exception: Role RQRequester is in use on a resource or group and cannot be deleted. (Note: there are 3 screenshots below)

 

To resolve, you need to remove role from the user and try again. follow these visual guides for the role removal process: (Note: there are 2 screenshots below)

That should be it!

In a recent Forbes article, Dr. T. Alexander Puutio, leadership professional and instructor at Harvard, Columbia and NYU, argues that the real AI revolution isn’t happening in splashy demos or hyped-up tools—it’s unfolding quietly inside the enterprise systems that keep global operations running. These “systems of record,” built to store and track information, are evolving into “systems of reason” that can interpret, predict, and guide decisions.

Puutio notes that while headlines focus on novelty, the deeper transformation is happening in the foundational software that industries like defense, construction, engineering, and government depend on. Companies are moving beyond dashboards and automation toward platforms that anticipate needs and provide meaningful foresight. AI is no longer valuable as a feature—it’s becoming the logic that shapes how work gets done.

He points to Deltek only as one example of this broader shift, but emphasizes that the pattern is industry-wide: organizations are rethinking architecture, not just adding tools. Modern AI demands systems built for reasoning, compliance, and intelligent workflow orchestration, not bolt-on chatbots.

Puutio also highlights insights from Kore.ai CEO Raj Koneru, who says legacy enterprise apps are facing “death by a thousand cuts” as AI permeates every layer of work. The next era of software, Koneru argues, will be defined by conversational interfaces, expanding context windows, and semi-autonomous workflows that intelligently bundle tasks while keeping humans in the loop.

The core message of Puutio’s piece is clear: the winners in enterprise AI will be those who redesign their foundations so intelligence is native, not an afterthought. When core systems begin to reason, organizations move from simply recording the past to proactively shaping the future.

For Full Article, Click Here

Candidates and suppliers from Landmark applications should not be synced to LSF. Services which allow users to register externally are services that should NOT be synced. If they were synced to LSF, follow the steps below to remove user and identity records from LSF.

Configure sync service lists to exclude candidates from sync – This process should be used if possible
Use Configure Services for Synchronization menu in ISS

Manual Sync service list configuration – This process may be used if not all services are shown in ISS
Export list of all services from LMK
 secadm -p <secadmpassword> service list
 The list outputs to the screen –copy the list from the screen into a text document
Determine which services from each system you DO want synced

Configure sync service lists for LSF and LMK in the LSF by adding the following lines to LAWDIR/system/lsservice.properties file:

 fed.LSFSERVERNAME.DOMAIN.COM;40000;40001;LSF. syncServiceList=YourListofLSFServicesToSync,SeparatedByCommas,NoSpaces fed.LMKSERVERNAME.DOMAIN.COM;10888;11888;LANDMARK. syncServiceList=YourListofLMKServicesToSync,SeparatedByCommas,NoSpaces

 Save changes and close lsservice.properties
Restart LSF and WAS

Configure tuning for sync*

  1. Add the following line to the LAWDIR/system/lsservice.properties

file: Nthread=5

This value can be any number between 2 and 10. You can tweak the Nthread parameter until you find the optimized setting for your system. Do not go above 10 unless directed by Infor.

  1. Adjust lase GRID node max heap to at least 3096

From the Grid Management main page go to Configuration Manager->Applications->Application->Landmark and the select the environment.
Select “Edit Properties.”
Under Grid Defined Properties -> Node Memory, select “Max Heap.”
Adjust the lase node memory to 3096 and then click Save
It may be set higher if number of users/identities indicates
-Restart the node for this environment or restart Landmark.

 

Many organizations adopt cloud ERP (enterprise resource planning) without the strategic governance needed to realize full value, leaving aging systems with declining satisfaction and hidden technical debt that internal reviews often miss. Achieving true ERP agility requires disciplined, reusable integration and strong data-quality standards to reduce costs and fully leverage cloud ecosystems. In a recent article on ERP Today, ERP writer and content director Tarsilla Moura reports on research by Infor, AWS, and Radar Group showing that many organizations are modernizing ERP in name only, with cloud adoption outpacing the strategic governance needed to drive real business value. The study finds that while 42% of organizations run ERP in the cloud, only 64% have a defined cloud strategy, leaving others to make ad-hoc decisions that increase costs and reduce control.

ERP systems often sit in a “mid-life comfort zone,” averaging 6.4 years old, with technical debt growing and satisfaction declining as systems age. Investment trends show that while overall technology budgets are rising, ERP spending lags, and initiatives like AI and ML are being pursued without the governance and integration readiness needed to unlock their full potential.

The research emphasizes that modernization is more than cloud hosting. ERP must be treated as a strategic business platform, supported by governance, integration standards, security models, and outcome-based KPIs. Recommendations include defining a clear ERP and cloud strategy, establishing decision rights, adopting a roadmap tied to business outcomes, and leveraging external assessments to expose blind spots.

Integration discipline emerges as the critical factor for ERP agility. Fragmented integrations drive costs and slow change, even in cloud-first environments. Treating integration as a product function—with reusable patterns, deprecation plans, and strong data-quality standards—ensures ERP can scale with business needs and fully leverage cloud ecosystems.

For IT leaders and ERP managers, the takeaway is clear: cloud adoption alone isn’t enough. Without structured governance and disciplined integration, ERP risks remaining a platform in place rather than a driver of operational improvement.

 

For Full Article, Click Here

The passwords in install.cfg are encrypted in later versions of lawson.  If these passwords change, it would be ideal to also change them in install.cfg so the next update doesn’t run into any issue. To do this, follow the instructions below:

First, Open a command line utility with Lawosn env variables set.

Then type in the command java -cp %GENDIR%/java/thirdParty/installer.jar com.lawson.delivery.secure.PasswordAdministrator -s %LAWDIR%/system/install.cfg

Enter the Lawson configuration password

Next, View or edit passwords.  You can show them in clear text by clicking the “Yes” radio button.

Click finish when done

Restart Lawson services, or reboot the server. This should make the necessary changes and prevent any issues.

Distributors that hold onto outdated enterprise resource planning (ERP) systems may feel they’re avoiding risk, but the hidden costs of inaction steadily erode visibility, agility, and margins—making a structured, phased modernization approach the key to turning that risk into long-term resilience. In a recent article on MDM.com, author Jon Byrd highlights this particular challenge that many distributors quietly face.

 

While keeping an aging ERP in place can feel like the “safer” choice, Byrd argues that inaction is far from neutral. Support fees climb, specialized expertise becomes harder to find, and outdated hardware lingers long past its intended lifespan. But the financial hit is only part of the story. Legacy systems limit real-time visibility, making it harder to respond quickly to supplier price shifts or margin pressures — a problem every IT director or operations leader has felt at some point. Integration challenges compound the issue. Modern capabilities like AI-driven insights, digital sales platforms, and advanced analytics don’t plug neatly into old architectures. IT teams end up maintaining brittle workarounds that consume time and budget while still failing to deliver true agility. Slow reporting cycles further drag down decision-making, often leaving organizations reacting well after competitors have moved. Add to that the looming issue of end-of-support timelines — and the security risks or pricey extended-support agreements that follow — and the “do nothing” strategy quickly starts siphoning value.

Byrd also acknowledges the real risks of ERP modernization: data inconsistencies, process redesign, employee resistance, and replacing heavily customized legacy functions. But distributors succeeding with cloud ERP approach the shift as a structured journey: upfront assessments, phased rollouts, strong data governance, and rigorous testing. The takeaway: legacy ERP doesn’t just limit growth — it actively erodes competitiveness. With customer expectations rising and uncertainty persisting, modernizing intentionally isn’t just an IT initiative; it’s a strategic necessity.

 

For Full Article, Click Here

Follow these simple steps to learn how to include Report ID in LBI Maintain Reports

  1. First, go into Tools when logged in as an admin and select “Reporting Services My Reports”.
  2. Under the “All” section in the Report Lists on the left side dash, click “Edit List” on the top right of the screen.

  3. Next, under “List Options” select “Columns”.
  4. Then select “Report Id” and click the right arrow in the middle of the screen:
  5. Click “Save and Exit” and then go to “Maintain Reports” in the Reporting Services Administration Report Management Menu.
  6. Now you’ll see all the Report ID’s on the right hand column:

 

That’s all there is to it!

Infor has been named a Leader for the fifth consecutive year in Gartner’s 2025 Magic Quadrant for Cloud ERP for Product-Centric Enterprises. The recognition underscores Infor’s consistent strength in delivering cloud-native, industry-tailored ERP solutions.

In Gartner’s 2025 Critical Capabilities report, Infor earned highest scores in three of seven use cases: Process Manufacturing, Project/Asset-Intensive Manufacturing, and ERP for Lower Midsize Enterprises ($50M–$250M). It also secured a #2 ranking in Discrete Manufacturing, maintaining top-tier status there for six consecutive years.

Rick Rider, Infor’s SVP of Product Management, emphasized that these honors reflect the company’s focus on modernizing operations with solutions like Infor Leap and Industry AI Agents, which help customers leverage cloud ERP while unlocking new efficiencies and growth opportunities.

Gartner’s analysis also highlighted market trends shaping ERP evolution, including generative and agentic AI, low-code development, process mining, and tighter integration capabilities. These features are increasingly crucial for organizations seeking agility, operational insight, and competitive advantage.

For IT leaders, ERP managers, and system administrators, Infor’s continued recognition signals a stable, innovation-driven partner capable of supporting complex manufacturing and distribution environments while staying ahead of emerging technology trends.

 

For Full Article, Click Here