It is possible that the query is a good one:
select
CS.Name0,
NAC.ServiceName0,
NAC.MACAddress0
from
dbo.v_GS_COMPUTER_SYSTEM CS
Join dbo.v_GS_NETWORK_ADAPTER_CONFIGURATION NAC on CS.ResourceID = NAC.ResourceID
But it is not clear how to make this query to add the web reporting.
Hi!
Help create a query to select the subnet. I use the following:
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.IPSubnets = "192.168.100.0"
but this only works with /24 subnet. I have many subnets /25 /26, and I can not automate this collection.
Hi!
When I add a new win7 wim file and the executive "distribute content", is created in C:\ SMSPKGSIG new folder (for example PRI00014.1). Copying process is interrupted and win7.wim size is 20MB !?
If I try to execute this win7.wim "Shedule Updates". I get the response "Failed to copy the image from the package source location to the siteserver machine."
OfflineServicingMgr.log:
There is an image associated with this schedule.
Total number of individual updates to be installed is 90.
STATMSG: ID=7903 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCM2012.LV SITE=GS0 PID=3884 TID=2968 GMTDATE=se mai 12 08:56:28.559 2012 ISTR0="GS000015" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
Package source location for image GS000015 is not writable. GLE=5
STATMSG: ID=7915 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCM2012.LV SITE=GS0 PID=3884 TID=2968 GMTDATE=se mai 12 08:56:28.568 2012 ISTR0="GS000015" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
Schedule processing failed
The problem is probably here:
Package source location for image GS000015 is not writable. GLE=5
What rights and where to be?
-------
Update:
Create a new sharing folder. I gave the right to sharing and security rights of every all / full. Began to work well. Lack of understanding of how SCCM authenticate. Although SCCM admin users and SCCM server account is given full rights.
Update2:
Sharing Permission change to Everyone to full controll.
Interestingly, with an account sccm2012 the authorization? Maybe the system!
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.