Search the Community
Showing results for tags 'NTFS'.
-
Hi, For over a week I have been trying to solve an issue with a new SCCM 2012 R2 install in my environment. The infrastructure is as follows. Windows 2008 R2 Server Enterprise patched to SP1 and all current updates SQL Server 2012 SP1 WSUS 3.0 SP2 + patches SCCM 2012 R2 - Single Site server running in HTTPS mode All running on one server hosted on VMware ESXi 5.1 Update 1 + VMware Tools 9.0.5 The install of SCCM itself is successful but when I try to install report service point role, the following error is logged. But there are NTFS partitions available, and there are no network issues. I have tried looking for srsp.log files but don't exist. I have completed uninstalled and reinstalled all server components (SQL, SCCM, WSUS, IE e.t.c) but with the same result. I would appreciate any help in resolving this. SMS_SITE_COMPONENT_MANAGER Site Component Manager could not find an NTFS partition on site system "\\xxxx.xxx.xx" to hold the Configuration Manager Server Components' files. Possible cause: The site system does not contain an NTFS partition. Solution: Using the Windows Disk Administrator, create an NTFS partition on the site system, or convert an existing FAT partition to NTFS. Possible cause: The site system is not exporting the default drive letter shares, such as "\\xxxx.xxx.xx\C$", "\\xxxx.xxx.xx\D$", and so on. Solution: You might have disabled the default drive letter shares for security purposes. Configuration Manager requires these shares. Please re-enable these shares using the Windows Disk Administrator. Possible cause: The site system is turned off, not connected to the network, or not functioning properly. Solution: Verify that the site system is turned on, connected to the network, and functioning properly. Possible cause: Site Component Manager does not have sufficient access rights to remotely administer the site system. Solution: Verify that the accounts are properly configured to allow the site server to remotely administer the site system. Possible cause: Network problems are preventing Site Component Manager from properly accessing the site system. Solution: Investigate and correct any problems on your network. SMS_SITE_COMPONENT_MANAGER Site Component Manager failed to configure site system "\\xxxx.xxx.xx" to receive Configuration Manager Server Components. Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager cannot install any Configuration Manager Server Components on this site system until the site system is configured successfully. Site Component Manager will automatically retry this operation in 60 minutes. To force Site Component Manager to immediately retry this operation, stop and restart Site Component Manager using the Configuration Manager Service Manager.
-
- SCCM 2012 R2
- ConfigMgr
-
(and 1 more)
Tagged with:
-
Our environment has some dedicated virtual machines acting as file servers only. The largest one still runs Server 2003, with three big virtual disk volumes. I'm beginning to deploy Server 2012 and one file-only server is working well, including file deduplication. I would hand-copy files from one server to the other, but sysadmins are a lazy lot and I wondered if I could just detach a volume from the 2003 server, attach it to the 2012 server, and enable 2012 deduplication on it. I would then recreate the shares on the 2012 server and hope that the file system permissions remained in tact; both servers are domain members. I'd also have to edit logon scripts and home folders to point to the new mappings; no big deal there, and I'd have to do that anyway. The underlying environment is vSphere 5.1, but I wouldn't expect the server VMs to behave differently if this were Hyper-V. --